[Bug 2087549] [NEW] [SRU] remove pam_lastlog.so from configuration for noble

[Tim Andersson]

Public bug reported:

[ Impact ]

 * The following line has been found in users logs when trying to log in to their systems:
   login[2449]: PAM unable to dlopen(pam_lastlog.so): /usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file or directory
   This results in users reporting that they cannot login to their systems. They can perhaps do so with other login methods (ssh, login, gdm, xdm, etc) that don't depend on the lastlog binary, but that doesn't suffice.

 * The upload fixes the issue by dropping pam_lastlog.so from all
config, as well as not installing the lastlog binary.

[ Test Plan ]

 * Install Trixie in a VM and try to log in post installation. Whether
or not login fails, check the journal for the aforementioned message, or
if you login via ssh, the last login message shouldn't appear.

[ Where problems could occur ]

 * If there were login methods entirely dependent on pam_lastlog.so, I
imagine users using these login methods would have trouble. Though this
pam config I don't believe is widely used.

 * TODO: add more info here

[ Other Info ]

 * TODO: potentially add more info here

** Affects: shadow (Ubuntu)
     Importance: Undecided
         Status: New

** Description changed:

  [ Impact ]
  
-  * The following line has been found in users logs when trying to log in to their systems:
-    login[2449]: PAM unable to dlopen(pam_lastlog.so): /usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file or directory
-    This results in users reporting that they cannot login to their systems. They can perhaps do so with other login methods (ssh, login, gdm, xdm, etc), but that doesn't suffice.
+  * The following line has been found in users logs when trying to log in to their systems:
+    login[2449]: PAM unable to dlopen(pam_lastlog.so): /usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file or directory
+    This results in users reporting that they cannot login to their systems. They can perhaps do so with other login methods (ssh, login, gdm, xdm, etc) that don't depend on the lastlog binary, but that doesn't suffice.
  
-  * The upload fixes the issue by dropping pam_lastlog.so from all
+  * The upload fixes the issue by dropping pam_lastlog.so from all
  config, as well as not installing the lastlog binary.
  
  [ Test Plan ]
  
-  * Install Trixie in a VM and try to log in post installation. Whether
- or not login fails, check the journal for the aforementioned message.
+  * Install Trixie in a VM and try to log in post installation. Whether
+ or not login fails, check the journal for the aforementioned message, or
+ if you login via ssh, the last login message shouldn't appear.
  
  [ Where problems could occur ]
  
-  * If there were login methods entirely dependent on pam_lastlog.so, I
+  * If there were login methods entirely dependent on pam_lastlog.so, I
  imagine users using these login methods would have trouble. Though this
  pam config I don't believe is widely used.
  
-  * TODO: add more info here
+  * TODO: add more info here
  
  [ Other Info ]
  
-  * TODO: potentially add more info here
+  * TODO: potentially add more info here

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/2087549

Title:
  [SRU] remove pam_lastlog.so from configuration for noble

Status in shadow package in Ubuntu:
  New

Bug description:
  [ Impact ]

   * The following line has been found in users logs when trying to log in to their systems:
     login[2449]: PAM unable to dlopen(pam_lastlog.so): /usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file or directory
     This results in users reporting that they cannot login to their systems. They can perhaps do so with other login methods (ssh, login, gdm, xdm, etc) that don't depend on the lastlog binary, but that doesn't suffice.

   * The upload fixes the issue by dropping pam_lastlog.so from all
  config, as well as not installing the lastlog binary.

  [ Test Plan ]

   * Install Trixie in a VM and try to log in post installation. Whether
  or not login fails, check the journal for the aforementioned message,
  or if you login via ssh, the last login message shouldn't appear.

  [ Where problems could occur ]

   * If there were login methods entirely dependent on pam_lastlog.so, I
  imagine users using these login methods would have trouble. Though
  this pam config I don't believe is widely used.

   * TODO: add more info here

  [ Other Info ]

   * TODO: potentially add more info here

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2087549/+subscriptions