3 ms·
To be clear - he's not advocating for a change to Linux or systemd. He's reiterating an already commonly accepted best practice going forward. ...which unfortu
by phendrenad2 5y ago
To be clear - he's not advocating for a change to Linux or systemd. He's reiterating an already commonly accepted best practice going forward.
...which unfortunately due to the Linux ecosystem, where people apparently like to inject code into running processes (https://skarnet.org/software/nsss/nsswitch.html https://skarnet.org/software/nsss/nsswitch.html) (can't imagine this is brittle at all), can cause your program to break if someone injects a module that doesn't ALSO follow this best practice into your program.
- tadfisher 5y agoSee also: PAM, probably a much more enticing target. I wonder if something like the eBPF compiler could be repurposed here, to generate lightweight "binaries" for a configuration that can be linked without needing to dynamically link their own dependencies at runtime.
- LukeShu 5y agoFew programs load PAM modules, essentially all programs load NSS modules.
- dale_glass 5y agoI really hope Poettering decides to fix PAM too. It's well overdue. IMO PAM should be replaced with a daemon. This way all the code that deals with authentication can be isolated into its own process, and my screensaver doesn't need root access to check my password against /etc/shadow. It'll also simplify SELinux settings.