RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

+++ This bug was initially created as a clone of Bug #834446 +++

Description of problem:

In http://docs.fedoraproject.org/en-US/Fedora/17/html-single/Installation_Guide/index.html#s1-kickstart2-options, under the auth ks directive section, this following text is included:

"To set up the SHA-512 hashing algorithm, run authconfig --passalgo=sha512 --kickstart. Remove the --enablemd5 option if it is present."  Something similar just above it is mentioned for sha256.

So why does just "auth --useshadow --passalgo=sha512" work while kickstarting?  Are the other instructions about running authconfig even needed?  They appear to be included in error.



Version-Release number of selected component (if applicable):

F17 Install guide

--- Additional comment from jreed on 2012-11-13 20:02:19 EST ---

Thanks for reporting this, Joshua. You're right, the description refers more to an entirely separate command than an option in a kickstart file.

Given that just entering "--passalgo=sha512" has worked for you (which certainly makes sense), I have removed the full command, including --kickstart, so it now just reads as follows:

"--passalgo= — specify sha256 to set up the SHA-256 hashing algorithm or sha512 to set up the SHA-512 hashing algorithm."

The commit is here: http://git.fedorahosted.org/cgit/docs/install-guide.git/commit/?id=e210fece6d1d6cbf2abe989921df74ced380eb5e