Comment 10 for bug 270328

Revision history for this message
Munzir Taha (منذر طه) (munzirtaha) wrote :

My current ecryptfs-utils version is 53-1ubuntu8
I didn't try to enable the kerberos_example profile or run auth-client-config manually.
Now, after reinstalling that ecryptfs-utils package, I managed to log again to my system which is why I believe it's related somewho to the problem. More important, now my common-auth is different. It conains:

#
# /etc/pam.d/common-auth - authentication settings common to all services
#
# This file is included from other service-specific PAM config files,
# and should contain a list of the authentication modules that define
# the central authentication scheme for use on the system
# (e.g., /etc/shadow, LDAP, Kerberos, etc.). The default is to use the
# traditional Unix authentication mechanisms.
#
# As of pam 1.0.1-5, 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.

# here are the per-package modules (the "Primary" block)
auth [success=1 default=ignore] pam_unix.so nullok_secure
# here's the fallback if no module succeeds
auth requisite pam_deny.so
# prime the stack with a positive return value if there isn't one already;
# this avoids us returning an error just because nothing sets a success code
# since the modules above will each just jump around
auth required pam_permit.so
# and here are more per-package modules (the "Additional" block)
auth optional pam_ecryptfs.so unwrap
# end of pam-auth-update config

But dpkg-reconfigure libpam-runtime still gives the same errors