[Pkg-shadow-devel] Bug#1068017: util-linux: please ship liblastlog2 packages
Chris Hofstaedtler
zeha at debian.org
Sat Mar 30 00:41:40 GMT 2024
Hi OpenSSH, shadow Maintainers,
On Sat, Mar 30, 2024 at 01:32:08AM +0100, Chris Hofstaedtler wrote:
> 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.
>
[..]
> 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?
Answering my own question, not quite.
Apparently, traditionally we have:
* sshd writes to /var/log/lastlog by itself.
* login has pam_lastlog.so in its PAM snippet.
Both of these would need to be replaced by pam_lastlog2.so. I don't
really know what the other distros are doing right now, and/or if
we should align on this.
So we could either put pam_lastlog2.so into a common-* file from
src:pam, or openssh and shadow should switch their setup.
What do we all think about that?
Chris
More information about the Pkg-shadow-devel
mailing list