Add no_new_privs
hardening to OpenRC and systemd service files #575
No reviewers
Labels
No labels
approved, awaiting change
bug
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs docs
needs tests
not a bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: AkkomaGang/akkoma#575
Loading…
Reference in a new issue
No description provided.
Delete branch "norm/akkoma:no-new-privs"
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?
Based on upstream Pleroma MR: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/3905
I also added in similar hardening to
installation/akkoma.service
as well since I don't see why that shouldn't be the case as well.This will help prevent the Akkoma processes from gaining additional privileges, making it easier to prevent privilege escalation attacks from happening.
3b54380c2a
to88cd8fa93b
88cd8fa93b
to0cb57b9fc3
0cb57b9fc3
toba505d2b1e
Just noticed that the systemd file did have that setting at one point but was removed in
e7b0840b88
because it apparently broke using sendmail.I'd argue that most admins don't use sendmail for their emails and there are ways to make sendmail work without set{u,g}id anyways. If someone has to use sendmail with set{u,g}id then they can disable it themselves, while the rest of us can have a mroe secure config.
ba505d2b1e
todb64556306
all good, thanks