Skip to content
This repository has been archived by the owner on Mar 6, 2023. It is now read-only.

Lock down systemd service #68

Merged
merged 1 commit into from
Jan 9, 2019
Merged

Conversation

ecksun
Copy link
Contributor

@ecksun ecksun commented Jan 8, 2019

To be on the safe side, restrict what the service can do.

@paulfantom
Copy link
Member

@ecksun ecksun force-pushed the master branch 2 times, most recently from bdad604 to 3d518d8 Compare January 8, 2019 18:55
@ecksun
Copy link
Contributor Author

ecksun commented Jan 8, 2019

I added ProtectControlGroups and ProtectKernelModules and changed ProtectSystem=strict.

Do you want me to do the check for an old systemd version also?

@paulfantom
Copy link
Member

systemd version check is necessary when using ProtectSystem=strict as strict was introduced in systemd 232

@ecksun
Copy link
Contributor Author

ecksun commented Jan 8, 2019

Alright, the other Protect directives also require 232 according to the changelog so I included them in the version check as well

tasks/preflight.yml Outdated Show resolved Hide resolved
templates/node_exporter.service.j2 Outdated Show resolved Hide resolved
To be on the safe side, restrict what the service can do.
@ecksun
Copy link
Contributor Author

ecksun commented Jan 9, 2019

I don't know if you get notifications for pushes, but I think I fixed your comments :)

@paulfantom paulfantom merged commit d1824cf into cloudalchemy:master Jan 9, 2019
@lock
Copy link

lock bot commented Mar 24, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants