>>>>> "Michael" == Michael Rasmussen <[email protected]> writes:
Michael> On Sun, Mar 08, 2009 at 06:19:35PM -0700, Bill Barry wrote: Bill> I had this exact same thing occur to me yesterday. I first Bill> noticed it when su took me directly to root. Having seen this Bill> thread, I went though the backups for the last few days and Bill> noticed that several files in /etc/pam.d had been updated during Bill> a normal debian upgrade. The files were etc/pam.d/common-account Bill> etc/pam.d/common-auth etc/pam.d/common-password Bill> etc/pam.d/common-session Bill> I restored these files from the backup and the problem Bill> disappeared. As far as I can tell this was not caused by any Bill> malice, but was caused by a packaging problem. Michael> packaging problem or compromised package? Coming from the Michael> package does not rule out malice. # # /etc/pam.d/common-account - authorization settings common to all services # # This file is included from other service-specific PAM config files, # and should contain a list of the authorization modules that define # the central access policy for use on the system. The default is to # only deny service to users whose accounts are expired in /etc/shadow. # # As of pam 1.0.1-6, this file is managed by pam-auth-update by default. # To take advantage of this, it is recommended that you configure any # local modules either before or after the default block, and use # pam-auth-update to manage selection of other modules. See # pam-auth-update(8) for details. # You might try grepping /var/lib/dpkg/info for pam-auth-update, maybe? -- Russell Senior, Secretary [email protected] _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
