Skip to content
New issue

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

Restrict systemd units as much as possible #1

Open
danstiner opened this issue Dec 28, 2017 · 1 comment
Open

Restrict systemd units as much as possible #1

danstiner opened this issue Dec 28, 2017 · 1 comment
Labels

Comments

@danstiner
Copy link
Owner

danstiner commented Dec 28, 2017

A number of good ideas in: http://0pointer.net/public/systemd-nluug-2014.pdf

Should be as simple as trying each mitigation and see which can be enabled without breaking anything.

Possibly more in the following presentation: http://ftp.nluug.nl/video/nluug/2014-11-20_nj14/zaal-2/5_Lennart_Poettering_-_Systemd.webm

@chrysn
Copy link

chrysn commented Jul 16, 2022

The system daemon probably doesn't really need to run as root (which the client currently checks for -- needlessly, AFAICT). If the system daemon gets handed an open file descriptor to /dev/uhid, that's about all the privileges it needs (and handing on that FD can probably be done in the systemd unit).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants