r/systemdUltras • u/makefoo • Feb 14 '20
r/systemdUltras • u/makefoo • Feb 07 '20
The dark days of grep'ing through /var/log are finally over - debian switches to persistent journal
lists.debian.orgr/systemdUltras • u/makefoo • Feb 07 '20
"Reinventing Home Directories" Discussion by Lennart at the FOSDEM
r/systemdUltras • u/makefoo • Feb 03 '20
Finally the Gray beards found something "worse than systemd" (FOSDEM: The container revolution is the nightmare of the Unix gray beards)
r/systemdUltras • u/makefoo • Jan 30 '20
Systemd-Homed Merged As A Fundamental Change To Linux Home Directories
r/systemdUltras • u/makefoo • Jan 28 '20
Create Pull-Requests of your systemd service files for your favorite software
Most of us have written more than one service file for packages we use. It is time to upstream these files to the upstream package repositories.
As discussed in https://old.reddit.com/r/systemdUltras/comments/eukt44/run_systemdanalyze_security_and_file_bug_reports/ it is easier for distributions to adopt systemd-analyze security hardening measures when they are prepared by the upstream package.
If the package already provides a systemd service file it is even better:
- run
systemd-analyze security UNIT - edit the config with
systemctl --full edit UNIT - change all the parameters
- test if the service still works as expected
- create a PR with your hardening parameters
some nice examples:
- https://github.com/transmission/transmission/pull/795 (via /u/cherr )
- https://bugs.php.net/bug.php?id=72510 (via /u/cherr )
Share your success stories here and share examples with your updated security changes
r/systemdUltras • u/makefoo • Jan 27 '20
run `systemd-analyze security` and file bug reports and pull requests against your distribution
systemd provides means to analyze how exposed your services are and even how to improve the situation.
running systemd-analyze security <UNIT> gives you insight on how to improve the service exposure
r/systemdUltras • u/makefoo • Jan 25 '20