Bug 452673 - Special Characters in Root password of kickstart fail
Special Characters in Root password of kickstart fail
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Server (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Partha Aji
Steve Salevan
Depends On:
Blocks: 454471 456985
  Show dependency treegraph
Reported: 2008-06-24 09:28 EDT by Patrick Connelly
Modified: 2010-10-22 22:11 EDT (History)
2 users (show)

See Also:
Fixed In Version: sat530
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-09-10 16:26:13 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Test script to compare satellite generated hash to openssl hash (779 bytes, text/plain)
2008-06-24 09:28 EDT, Patrick Connelly
no flags Details

  None (edit)
Description Patrick Connelly 2008-06-24 09:28:40 EDT
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):

How reproducible:

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
Comment 1 Patrick Connelly 2008-06-24 09:28:40 EDT
Created attachment 310140 [details]
Test script to compare satellite generated hash to openssl hash
Comment 2 Patrick Connelly 2008-06-24 10:10:05 EDT
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'
Comment 6 Partha Aji 2008-07-23 19:50:05 EDT
Fixed the form and the action to makesure password doesnot get scrubbed..
Comment 10 Steve Salevan 2009-02-13 10:48:30 EST
Hash shown to be correct on 530-re20090206.1 and machine successfully kickstarted with password of '<>(){}'; moving to VERIFIED.
Comment 11 Sayli Karmarkar 2009-07-31 16:38:01 EDT
Kickstarted with "<({sayli})>" as passwd successfully.
Comment 12 Brandon Perkins 2009-09-10 16:26:13 EDT
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.


Note You need to log in before you can comment on or make changes to this bug.