> Hi. > Pam 1.5.3 adds support for using logind rather than utmp for a > couple > of things: > > * Counting the number of user sessions in pam_issue > > * Determining the time at which the user logged in in pam_timestamp. > > > If we did use logind, that would mean a dependency from libpam- > modules > to libsystemd. > > It would also mean pam_timestamp would not be very useful on systems > where logind was not actively used. > > Thoughts?
Yes we definitely should, as this is needed to solve Y2038, in case you missed it the PAM maintainer talked about this workstream at ASG the other day: https://www.youtube.com/watch?v=AdUmKczNwhg Various replacements for these legacy interfaces are being put in place in various projects like PAM, util-linux and so on, and logind is one of the replacements (there are more). -- Kind regards, Luca Boccassi
