Bug 500176
Summary: | RFE: Update auth / authconfig kickstart options to include sha256 and/or sha512 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Jim Perrin <james.l.perrin> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Release Test Team <release-test-team-automation> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.3 | CC: | ddumas |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-05-19 15:10:58 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jim Perrin
2009-05-11 14:18:01 UTC
The next major release of RHEL will no longer have these constraints, nor will it miss future parameters added to the authconfig command. Instead of parsing that line ourselves and then passing it on to authconfig, we just pass the entire string on and let authconfig worry about whether it supports a given parameter or not. This is a bit of a large change to go into an update release so it probably won't get backported. Just supporting these options is easier, but leaves us open to similar issues in the future. So I'd prefer to just deal with this in RHEL6 if at all possible. If you do require this change in an update release of RHEL5, please speak with your support representative who will be happy to raise this through the appropriate channels so we can deal with the scheduling of it. Thanks for the bug report. |