842067e675
Why this change --------------- Assumption - PAM's auth stack is properly configured. Currently account pam_systemd_home.so returns PAM_SUCCESS for non systemd-homed users, and a variety of return values (including PAM_SUCCESS) for homed users. account pam_unix returns PAM_AUTHINFO_UNAVAIL for systemd-homed users, and a variety of return values (including PAM_AUTHINFO_UNAVAIL) for normal users. No possible combination in the pam stack can let us preserve the various return values of the modules. For example, the configuration mentioned in the manpage causes account pam_unix to never be reached since pam_systemd_home just returns a success for ordinary users. Users with expired passwords are allowed to log in because a check cannot be made. More configuration examples and why they don't work are mentioned in #16906 and the downstream discussion linked there. After this change ----------------- account pam_unix will continue to return wrong value for homed users. But we can skip the module conditionally using the return value from account pam_systemd_home. We can already do this with the auth and password modules.
System and Service Manager
Details
Most documentation is available on systemd's web site.
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 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 or join our IRC channel.
Stable branches with backported patches are available in the stable repo.