Description of problem: When adding any of the following characters to the root password of a kickstart, the md5 hash is generated incorrectly. < > ( ) { } Version-Release number of selected component (if applicable): rhns-server-5.1.0-57 How reproducible: Everytime Steps to Reproduce: 1. Set root password in kickstart to contain any of the above characters 2. Kickstart machine 3. Try to login as root 4. Look at rootpw line in kickstart 5. Verify output with openssl echo "password" | openssl passwd -salt saltfromks -1 -stdin Actual results: Sets the incorrect root password Expected results: Sets the correct root password Additional info: When editing the kickstart's password, the number of "dots" will drop on the "Verify New Root Password" box if one of the password characters fails. Attached script will show the hash from the satellite, as well as the "correct" hash
Created attachment 310140 [details] Test script to compare satellite generated hash to openssl hash
After a little more digging, it appears that the WebUI completely ignores the character and sets the password as if it was not entered. IE. A password of 'aaaa(' is stored and hashed as if it was 'aaaa'
Fixed the form and the action to makesure password doesnot get scrubbed..
Hash shown to be correct on 530-re20090206.1 and machine successfully kickstarted with password of '<>(){}'; moving to VERIFIED.
Kickstarted with "<({sayli})>" as passwd successfully.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHEA-2009-1434.html