Base64 encoded Passwords get re-encoded on unattended/built call
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.
#2 Updated by Dominic Cleal over 4 years ago
- 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.