Password not being set right
I've got an issue where my password for root isn't being set right. Or
at all for that matter. My autoinstall file has the following
sections:
<security>
Jesse, I am replying here, to close this issue on the list rather than on private email. It seems you start with a full control file with all the post configuration stuff like security and users and create a modified new version of the profile in the pre-script like I described earlier on this list. But it seems the new modified control only has minimal configuration (partitioning and software) and none of the initial data, so no wonder nothing is configured when the system reboots... The modified profile HAS to be a full profile, and not just a subset. Maybe I was not clear when I described how to do it. The way you thought it works is actually not a bad idea and will think about adding it someday, but for now, modified.xml has to be a full profile. Anas Jesse Keating wrote:
I've got an issue where my password for root isn't being set right. Or at all for that matter. My autoinstall file has the following sections:
<security>
reboot /usr/lib/cracklib_dict no no no yes 3 yes 60000 101 all yes yes 99999 12 0 5 7 md5 yes secure nobody 60000 100 </security><users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <username>root</username>
$1$QyzzjhWY$/wFY11PqReGKyxDSydLgh. <forename></forename> <surname></surname> </user> </users>However once my system installs, root has NO password. And furthermore, if I run yast2 on the installed system, it would appear that the password encription is set to DES rather than MD5. Is this just flatly ignored, and since my password is too long for DES I get no password instead? Please help me to understand what is going on here.
On Friday 29 October 2004 19:58, Anas Nashif wrote:
Jesse, I am replying here, to close this issue on the list rather than on private email.
It seems you start with a full control file with all the post configuration stuff like security and users and create a modified new version of the profile in the pre-script like I described earlier on this list. But it seems the new modified control only has minimal configuration (partitioning and software) and none of the initial data, so no wonder nothing is configured when the system reboots...
The modified profile HAS to be a full profile, and not just a subset. Maybe I was not clear when I described how to do it. The way you thought it works is actually not a bad idea and will think about adding it someday, but for now, modified.xml has to be a full profile.
Ah, I see. Thats not _too_ terrible a thing, now that I know thats how it works I can hack around it. One last thing that is bothering me, how can I ensure that a graphical install env is used? My system(s) support graphical install, however I have yet to see graphical install with autoinstall work. -- Jesse Keating RHCE Pogo Linux -- Linux Systems Engineer tel: (888) 828-7646 ex: 436
participants (2)
-
Anas Nashif
-
Jesse Keating