Notice in my post I said "I am not using shadow"? In the case that you don't use shadow passwords, they are stored in /etc/passwd. In addition, if I *were* using shadow, I believe the entry in /etc/passwd would not be a '*' it would be a '+'.
The crypted string is grabbed from root's /etc/passwd entry on the system where I generate the kickstart file - this is done via a script and has worked with RH8, RH9, RHEL3 and RHEL4. Thanks, Kevin -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hugh Brown Sent: Monday, June 11, 2007 5:38 PM To: Red Hat Enterprise Linux 5 (Tikanga) discussion mailing-list Subject: Re: [rhelv5-list] Root password locked after kickstart! Passwords are usu. stored in /etc/shadow not in /etc/passwd How did you generate the crypted_string_here password? Hugh Collins, Kevin [MindWorks] wrote: > Hi, > > I'm not thru my second kickstart installation of RHEL 5, and in > both cases the root password has been locked (i.e., passwd hash in > /etc/passwd is '*') upon completion of the installation. I am not using > shadow or MD5 hashes. The relavent lines from the kickstart file are : > > rootpw --iscrypted crypted_string_here > authconfig --enableldap --enableldapauth --ldapserver=$LDAP > --ldapbasedn="dc=my,dc=domain" > > > Note that I have replaced the crypt'd hash with the string > "crypted_string_here" and replaced my actual LDAP domain in the lines > above. > > I have read the release notes and searched bugzilla - did not find > anything. Anyone else seeing this behaviour? > > Thanks, > > Kevin > _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
