Bug #11715
closed
Base64 encoded Passwords get re-encoded on unattended/built call
Added by Nils Domrose over 9 years ago.
Updated almost 7 years ago.
Description
Base64 encoded Passwords (i.e. used for windows template deployments) get re-encoded after a call to the built URL is made resulting in Base64 in Base64 encoded passwords.
Steps to reproduce:
- create a operatingsystem with hash type base64
- create a machine and set a password
- as long as the machine is in status "build" the root_pass is only encoded once.
- If a call to unattended/built is made, the root_pass is base64 encoded twice.
This is normally not a problem but I think it is not an intended behaviour.
- Related to Feature #8890: Allow selection of plaintext "encryption" method for root password added
- Category set to Host creation
Looks like a bug in the host which calls the crypt method. It normally checks for a regular crypt call if the password already has a $..$ type form, but obviously, that won't work for plain base64 so it's calling crypt each time the host is edited.
Thanks for writing this up Nils. Is there a suggestion for a workaround until something gets merged in? Right now we're having to hard-code a default password in the template, then change it later with puppet which is not ideal.
- Assignee set to Tom Caspy
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/2695 added
- Pull request deleted (
)
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
- Translation missing: en.field_release set to 88
Also available in: Atom
PDF