Add no_new_privs hardening to OpenRC and systemd service files #575

Merged
floatingghost merged 3 commits from norm/akkoma:no-new-privs into develop 2023-07-27 12:54:45 +00:00
Contributor

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.

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.
norm force-pushed no-new-privs from 3b54380c2a to 88cd8fa93b 2023-06-29 06:26:49 +00:00 Compare
norm force-pushed no-new-privs from 88cd8fa93b to 0cb57b9fc3 2023-06-29 06:27:48 +00:00 Compare
norm force-pushed no-new-privs from 0cb57b9fc3 to ba505d2b1e 2023-06-29 06:30:53 +00:00 Compare
Author
Contributor

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.

Just noticed that the systemd file did have that setting at one point but was removed in e7b0840b88838f9e14bd2b09060d89c4a656966c 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.
norm force-pushed no-new-privs from ba505d2b1e to db64556306 2023-07-22 06:41:44 +00:00 Compare

all good, thanks

all good, thanks
floatingghost merged commit 597a97cca9 into develop 2023-07-27 12:54:45 +00:00
floatingghost deleted branch no-new-privs 2023-07-27 12:54:45 +00:00
Sign in to join this conversation.
No description provided.