| Summary: | Unable to change ssh key password while in FIPS mode (fips=1) | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Ricky Nelson <rnelson> |
| Component: | openssl | Assignee: | Tomas Mraz <tmraz> |
| Status: | CLOSED ERRATA | QA Contact: | Miroslav Vadkerti <mvadkert> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.2 | CC: | cww, jjaburek, ksrot, mvadkert, syeghiay, tmraz |
| Target Milestone: | rc | Keywords: | Regression, ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | openssl-1.0.0-26.el6 | Doc Type: | Bug Fix |
| Doc Text: |
This was already documented in the Z-stream errata.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-02-21 10:43:11 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 836160, 848406 | ||
|
Description
Ricky Nelson
2012-04-13 13:22:29 UTC
This seems to be problem with used key format in OpenSSL. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. It has been proposed for the next release. If you would like it considered as an exception in the current release, please ask your support representative. The workaround: umask 077 openssl genrsa 2048 | openssl pkcs8 -topk8 -v2 aes128 -out rsa restorecon rsa ssh-keygen -y -f rsa > rsa.pub This creates a key in pkcs8 format even on rhel-6. Of course changing the passphrase with ssh-keygen is not possible - the openssl pkcs8 command has to be used instead. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0443.html |