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.

Description of problem:


Version-Release number of selected component (if applicable):
openssh-5.3p1-70.el6_2.2.x86_64

How reproducible:
Enable FIPS (fips=1 on kernel line), create an ssh key with a valid password, then attempt to change the password. This fails with 'Bad passphrase.'

Steps to Reproduce:

[root@dhcp209-46 ~]# cat /proc/sys/crypto/fips_enabled
1

[root@dhcp209-46 ~]# ssh-keygen -t rsa -f rsa -b 2048
Generating public/private rsa key pair.
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in rsa.
Your public key has been saved in rsa.pub.
The key SHA1 fingerprint is:
f6:f5:cb:d1:ce:79:a0:9f:f4:ed:18:64:79:39:ac:7e:d2:c7:61:6f root.pnq.redhat.com
The key's SHA1 randomart image is:
+--[ RSA 2048]----+
|                 |
|                 |
|                 |
|              ...|
|        S   . ++.|
|       . . . +o=.|
|          .  oBo+|
|            o+ %E|
|             oO+O|
+-----------------+

root@dhcp209-46 ~]# ssh-keygen -p -f rsa
Enter old passphrase:
Bad passphrase.


Expected results:
Should be able to change an ssh key password.

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