Lennart Poettering
34e5f14c34
PAM is a bit quirky: the main libpam calls are pam_authenticate(), pam_open_session(), pam_acctmgmt(), pam_chauthtok(), pam_setcred() and each have their own PAM "management group" in PAM configuration files that configure the modules to call: "auth", "account", "session", "password" – except for pam_setcred() which shares its grpup with pam_authenticate() and uses "auth". Both our PAM configuration files we ship by default are never used for authentication (they just appear in PAMname= in a service to get a PAM session set up, and PAMName= never calls pam_authenticate()). However, they end up being used for pam_setcreds() (because some modules want to use that the service manager calls it). So far we used the pam_deny module for the "auth" management group for these two PA; configurations (sinced6aed1dca8) but that's not ideal, since it means we'll always cause pam_setcreds() to fail which will create debug log noise (since the service manager debug logs pam_secreds() failures). Let's switch to pam_rootok for this instead. This has the benefit that pam_setcred() will always succeed for this, and pam_authenticate() only if the caller is root anyway. This is great, because it means our PAM configuration cannot be misused for other purposes accidentally (authentication will fail, unless you are already root), but won't result in any log noise (debug or otherwise). Follow-up for:d6aed1dca8Fixes: #39617
System and Service Manager
Details
Most documentation is available on systemd's website.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS, and also repositories with packages built from the latest stable release