Bug #1171
support sha512 password hashing in RHEL6 / CentOS6
| Status: | Duplicate | Start: | 09/17/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assigned to: | - | % Done: | 0% |
|
| Category: | Host creation | |||
| Target version: | - | |||
| Backlog: | No | Difficulity: | ||
| Votes: | 0 |
Description
Currently, foreman doesn't support the "default" hashing algo used by RHEL6.
If you use the following line in your kickstart:
authconfig --useshadow --passalgo=sha512
The resulting encrypted path will not be using sha512, which means you'll get authentication errors when the host is provisioned.
My workaround right now, is to NOT let foreman encrypt the passwords.
I have foreman set the initial password to "password" (in plaintext)
rootpw password
And then on the first puppet run, I have a module that changes the password to what it should be, using SHA512.
Related issues
| duplicates Foreman - Feature #2127: Support newer hash schemes for root passwords | New | 01/15/2013 |
History
Updated by Ohad Levy over 1 year ago
- Target version deleted (
0.4)
Updated by Ohad Levy over 1 year ago
I'm not sure I could reproduce this (e.g. it works with the default templates just fine), what am I missing?
Updated by Benjamin Papillon 4 months ago
- Status changed from New to Duplicate
