Description of problem: If ks file generated by anaconda on RHEL6 gets uploaded to Satellite, the following warn message shows up: "This kickstart profile uses a different type of encryption by default than the root password is currently using. You must reset the root password to encrypt it with the new method." See the attached picture. Note: By default anaconda on rhel6 uses sha512 algo for rootpw. Version-Release number of selected component (if applicable): 2.5 How reproducible: Always Steps to Reproduce: 1. Install some RHEL6 machine to get ks file or generate it or make sure that already existing one contains sha512 algo (starts with "$6"): rootpw --iscrypted $6$trAlalaT$RaLaLAtraLALaTR4lALATr4LAlatraLALaTR4lALATr4LAltraLALaTR4lALATr4LAltraLALaTR4lALATr4LA 2. Upload it to the Spacewalk: https://<input_your_sat_fqdn>/rhn/kickstart/AdvancedModeCreate.do 3. Switch to "Kickstart File" tab: https://<input_your_sat_fqdn>/rhn/kickstart/KickstartFileDownloadAdvanced.do?ksid=<input_ks_id> Actual results: The following warn message gets printed: "This kickstart profile uses a different type of encryption by default than the root password is currently using. You must reset the root password to encrypt it with the new method." Expected results: No warn message if anaconda uses sha512 on RHEL6 by default.
Taking...
spacewalk.git: 23bcc689857463608c23ee8090ad4af354f5dd5a
1) Add commit with small fix: cbc62debb44e26224c0785d7610e94e0f9f96a41 2) Add fix for backward compatibility: 2e27bc7c4a13477c64f4c707dcfd4df649cd1199
Verified by reproducer from the initial report, using spacewalk-java-2.6.48-1. Used a sample kickstart file with "rootpw --iscrypted" option encrypted with sha512 (encrypted string format is $6$<salt>$<encrypted_password>). There is no error message now. Both $6... and $5... are accepted without an error. VERIFED
This looks like it was fixed in previous release, but I'm closing it in this one. Spacewalk 2.7 has been released. https://github.com/spacewalkproject/spacewalk/wiki/ReleaseNotes27
*** Bug 1304505 has been marked as a duplicate of this bug. ***