gtnh-service-hardening #36
No reviewers
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Lithium/nixosConfig!36
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "gtnh-service-hardening"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hardening the service to prevent escape hatches
outside locations
to prevent abusing privilege escalation exploits or techniques
This is probably as good as it gets for security.
This makes most exploits unusable.
It's probably a good idea to look into whether you can add or remove sudo from specific users.
It'd be really useful to be able to completely neuter a user from privilege escalation without rarely available RCEs.
In the end, the better way is to run the server inside a virtual machine.
The extra image size is barely anything if we keep to a minimal image.
We could also remove the tmux requirements by using a different linux distribution.
LGTM
gtnh-service-hardeningto WIP: gtnh-service-hardeningWIP: gtnh-service-hardeningto gtnh-service-hardeningPull request closed