Hi Sven, Hi Sam, Steve, On Fri, Mar 29, 2024 at 06:02:39PM +0100, Sven Joachim wrote: > It seems desirable to ship liblastlog2 in trixie, considering that the > /var/log/lastlog file is not Y2038-safe and pam in unstable has already > dropped pam_lastlog.so, meaning that non-ssh logins are no longer > recorded in /var/log/lastlog. > > I have not looked closely yet, but I guess that would mean additional > packages liblastlog2-2 for the library, liblastlog2-dev for the > development files and libpam-lastlog2 for the pam module. The lastlog2 > binary could probably be included in util-linux-extra.
I generally agree that we should ship lastlog2 and the pam module. But this needs to be happen coordinated with src:pam. Installing the modules and the binary and not using them is not a good plan. At the same time, all traditional writing to /var/log/lastlog should stop. So, after some of the current fog clears, src:util-linux could introduce new binary packages (at least libpam-lastlog2), but src:pam would need to add it to the common-* config files. Does this seem right? PAM Maintainers, do you agree with this plan? Which timing would work for you? Chris PS: the bug never made it into my mailbox. If necessary, please poke on IRC.
