This used to be a normal announcement on vtty login. On Trixie it's missing. What's responsible for it?
Is it different on Trixie?
This used to be a normal announcement on vtty login. On Trixie it's
missing.
On Tue, Nov 05, 2024 at 08:17:57 -0500, Felix Miata wrote:
This used to be a normal announcement on vtty login. On Trixie it's missing. >> What's responsible for it?
I think it's part of /etc/pam.d/login . On Debian 12, that file
includes this bit:
# Prints the last login info upon successful login
# (Replaces the `LASTLOG_ENAB' option from login.defs)
session optional pam_lastlog.so
I'm not *certain* that's it, but it looks like it.It certainly appears it must work differently on Trixie.
Is it different on Trixie?
No idea. I don't run testing unless it's really close to release.
On Tue, 5 Nov 2024 08:17:57 -0500 Felix Miata wrote:
This used to be a normal announcement on vtty login. On Trixie it's
missing.
Odd. It's present on the VM I recently installed using a recent weekly
build, "testing _Trixie_ - Official Snapshot amd64 NETINST with
firmware 20241028-03:22]".
Greg Wooledge composed on 2024-11-05 08:27 (UTC-0500):
On Tue, Nov 05, 2024 at 08:17:57 -0500, Felix Miata wrote:
This used to be a normal announcement on vtty login. On Trixie it's missing.
What's responsible for it?
I think it's part of /etc/pam.d/login . On Debian 12, that file
includes this bit:
# Prints the last login info upon successful login
# (Replaces the `LASTLOG_ENAB' option from login.defs)
session optional pam_lastlog.so
String lastlog is absent from that file here, same as the file's section you quoted. According to apt-file, there is no pam_lastlog.so on the system either,
which in Bookworm is provided by libpam-modules, which is installed on Trixie.
I'm not *certain* that's it, but it looks like it.
Is it different on Trixie?
No idea. I don't run testing unless it's really close to release.It certainly appears it must work differently on Trixie.
On Tue, 5 Nov 2024 08:17:57 -0500
Felix Miata <[email protected]> wrote:
This used to be a normal announcement on vtty login. On Trixie it's missing.
Odd. It's present on the VM I recently installed using a recent weekly
build, "testing _Trixie_ - Official Snapshot amd64 NETINST with
firmware 20241028-03:22]".
This used to be a normal announcement on vtty login. On Trixie it's missing. What's responsible for it? Is it different on Trixie? On Tumbleweed it's a separate package lastlog or something like that. Search for similar for Trixie
comes up empty. :(
I believe the message in SSH is due to /etc/ssh/sshd_config. Search
for "banner."
Felix Miata composed on 2024-11-05 08:17 (UTC-0500):
This used to be a normal announcement on vtty login. On Trixie it's missing. >> What's responsible for it? Is it different on Trixie? On Tumbleweed it's a >> separate package lastlog or something like that. Search for similar for Trixie
comes up empty. :(
I don't know how I managed to come up empty, but on retry after reading thread
replies, two I should have found turned up - libpam-lastlog2 & liblastlog2-2. Now
in /etc/pam.d/common-session I have the session optional pam_lastlog.so that Greg
pointed to, but after systemctl daemon-reload, no change, and also no change after
reboot. systemctl list-unit-files | grep last returns null. There's no man page
for common-session. pam-auth-update common-session has (and had), "Maintain lastlog2 database" enabled, yet still no last login after another reboot to multi-user.target. / filesystem has Inode size 128. Could that be it? Nope. I was
able to change it to 256 with tune2fs, but still no last login after yet another
reboot. :(
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 715 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 165:34:36 |
| Calls: | 12,096 |
| Calls today: | 4 |
| Files: | 15,001 |
| Messages: | 6,517,806 |