Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Once systemd-232 is merged (#20156) and things are working, we have a bunch of tasks:
The text was updated successfully, but these errors were encountered:
This is the best practice list from the mailing list:
CapabilityBoundingSet=... MemoryDenyWriteExecute=yes NoNewPrivileges=yes PrivateDevices=yes PrivateTmp=yes PrivateUsers=yes ProtectControlGroups=yes ProtectHome=yes ProtectKernelModules=yes ProtectKernelTunables=yes ProtectSystem=strict RestrictAddressFamilies=AF_NETLINK AF_UNIX RestrictNamespaces=yes RestrictRealtime=yes SystemCallFilter=~@clock @cpu-emulation @debug @keyring @module @mount @obsolete @raw-io @resources
Sorry, something went wrong.
systemd 232 is on staging (a38f191)
We are on systemd-239 now. Is this still relevant?
Very much so - we are not really making use of the various capabilities to lock things down (yet).
infinisil
No branches or pull requests
Once systemd-232 is merged (#20156) and things are working, we have a bunch of tasks:
The text was updated successfully, but these errors were encountered: