Bug #1084
closedOpenSUSE / SLES deployment root password not working
Description
Hi,
I noticed that the root password entered in the host creation phase is not correctly applied to the deployed machine. I guess because SUSE is using a different alogorithm as the one that is used in foreman. Maybe Suse is using md5sum. I googled a lot for it but couldn't find any clear details what is used in Suse.
Regards,
Oliver
Updated by Ohad Levy over 13 years ago
You are probably correct, the handling of encoding the password should be moved away to the OS layer, so each OS should handle the encryption it self.
I'm assuming most OS's support md5sum, and only solaris is still on crypt, however I'm not certain, would be great if anyone could contribute some knowledge here :)
Updated by Oliver Weinmann over 13 years ago
Hi Ohad,
I just deployed a new machine (SLES 11) I'm testing some things with provisioning here. Now the password worked. I found a type in the default OpenSUSE Provisioning template. Maybe the typo was my mistake?
I changed:
<%= root_pass %>/
to:
<%= root_pass %>
Now it works. :)
Updated by Ohad Levy over 13 years ago
- Category set to Unattended installations
- Target version set to 0.4
great, do you want to send a git patch?
Updated by Oliver Weinmann over 13 years ago
I would love to. But I have no clue how to do this. :)
Updated by Ohad Levy over 13 years ago
something like:
read though Contribute
and then something like this:
cd /tmp git clone git://github.com/ohadlevy/foreman.git foreman cd foreman vim app/views/unattended/autoyast.xml.erb git diff git ci app/views/unattended/autoyast.xml.erb -m "fixes #1084 - OpenSUSE / SLES deployment root password not working" rake mail_patches
Updated by Ohad Levy about 13 years ago
sadly i never got the patch, mind attaching the git formatted patch here instead ?
Updated by Ohad Levy about 13 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset 72e1d32da42ac1c6f2d0ef7768ff03b95ac05793.