Bugzilla – Bug 5507
Something replaces /etc/login.defs
Last modified: 2004-02-25 07:59:52 UTC
/etc/login.defs originally has the following defined (originally as in from a clean install of SMGL [any ISO]): MD5_CRYPT_ENAB yes However, both KallDrexx and I noticed that after installing Linux-PAM (neither of us tested it before, but KallDrexx accidently ran across it after LP was installed) that it was later set to "no". The "shadow" package installs a copy of /etc/login.defs, so it may be from here, as even after removing Linux-PAM and recasting shadow (with "-r -c"), the problem presists.
Anybody running PAM want to propose a fix?
I have PAM installed so i'll take a look. I'll post back here before I actually change anything though. I guess I expected sandalle or Kalldrexx to acutally follow this up and find out what was changing it.
I have checked the 0.8 ISO and the login.defs{linux} files both have md5_crypt off. #MD5_CRYPT_ENAB no My login.defs was installed when I manually rebuilt a 0.5.1 ISO to my hardware specs then burned it and installed cleanly has MD5_CRYPT_ENAB yes. This was a previous bug http://bugs.sourcemage.org/show_bug.cgi?id=1086 where you (sandalle) verified it was correctly set in 0.6-beta3 it appears to have suffered a reversion since then. I think the spell was never fixed because login.defs was always an untracked file from the initial install and only with Benoit's removal of alien files from the ISO has this become a bug. I have now changed the spell and the file on the ISO will need to be updated for 0.9
you all might have noticed I have not closed this bug, even though I have fixed the spell. I think it should be closed by the ISO/Cauldron team when they release an ISO that has the corrected file on it.
Sounds good. I just haven't had time to look into this since I reported it.
Laurent, does the 0.9 ISO have this file fixed on it?
Assigning to ISO Team as it's in their court now.
fixed in the 0.9.1 ISO someone please verify ?
I'll try to install 0.9.1 on this machine (which uses LVM), and if not, I have another machine I can try to setup, but no guarantee on time (busy), so if someone else could... ;)
been three weeks, closing.