pam_lastlog.so was dropped by upstream in 1.5.3[1]. It's still there in the code, but not built by default.
And indeed, in noble (1.5.3) we don't have it, while mantic (1.5.2) does.
This does not prevent console logins, but generates an error in the logs:
Apr 23 20:02:09 n1 login[835]: PAM unable to dlopen(pam_lastlog.so): /usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file or directory
Apr 23 20:02:09 n1 login[835]: PAM adding faulty module: pam_lastlog.so
Debian's shadow package is also still shipping this config[2].
pam_lastlog.so was dropped by upstream in 1.5.3[1]. It's still there in the code, but not built by default.
And indeed, in noble (1.5.3) we don't have it, while mantic (1.5.2) does.
This does not prevent console logins, but generates an error in the logs: pam_lastlog. so): /usr/lib/ security/ pam_lastlog. so: cannot open shared object file: No such file or directory
Apr 23 20:02:09 n1 login[835]: PAM unable to dlopen(
Apr 23 20:02:09 n1 login[835]: PAM adding faulty module: pam_lastlog.so
Debian's shadow package is also still shipping this config[2].
1. https:/ /github. com/linux- pam/linux- pam/blob/ cec36a8cd2c69cc 87eacc21da47133 4fbef128ee/ NEWS#L65 /salsa. debian. org/debian/ shadow/ -/blob/ master/ debian/ login.pam? ref_type= heads#L82
2. https:/