On Thu, Jan 12, 2012 at 10:26:58AM +1100, Jakub Wilk wrote: > * Vincent McIntyre <[email protected]>, 2010-11-05, 13:18: > >I used the default /etc/security/pam_unix2 file; > > % sudo mv /etc/security/pam_unix2.default /etc/security/pam_unix2 > > You are not supposed to rename this file. The PAM module reads the > /etc/security/pam_unix2.default file (yes, with ".default" suffix).
Thanks for this information. I can't recall why I thought that it was necessary to rename it. > > % grep -v ^# /etc/security/pam_unix2.default > > CRYPT=des > > CRYPT_FILES=blowfish > > BLOWFISH_CRYPT_FILES=5 > > CRYPT_YP=des > > Now I'm confused. So you renamed pam_unix2.default to pam_unix2, but the > former file is still there? > I think that there is a cut/paste error there or the line above. Apologies for the confusion. I went back to a clean system and reinstalled libpam-unix2. This time I didn't do any renaming of files. # grep -v ^# /etc/security/pam_unix2.default CRYPT=des CRYPT_FILES=blowfish BLOWFISH_CRYPT_FILES=5 CRYPT_YP=des # grep -v ^# common-password password required pam_unix2.so nullok debug I did not recreate the /etc/default/passwd symlink. I think now that I did it before because the NEWS file mentions it: Version 1.21 * Read /etc/default/passwd for default crypt hash method but the pam_unix2(8) manpage doesn't. I added a local user. $2$ is shown in /etc/shadow. I updated the password of an existing local user. This user had $1$ in /etc/shadow initially, after the update it had $2$. So I think this bug can be closed, as invalid. Thanks for your input, and sorry for the noise. Vince -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
