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.
Bug 1732424 - ssh-keygen -A fails in FIPS mode because of DSA key
Summary: ssh-keygen -A fails in FIPS mode because of DSA key
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: openssh
Version: 8.1
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: 8.0
Assignee: Jakub Jelen
QA Contact: Ivan Nikolchev
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-23 11:00 UTC by Ondrej Moriš
Modified: 2020-11-14 08:08 UTC (History)
2 users (show)

Fixed In Version: openssh-8.0p1-3.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 22:41:32 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
proposed patch (697 bytes, patch)
2019-07-23 13:02 UTC, Jakub Jelen
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:3702 0 None None None 2019-11-05 22:42:00 UTC

Description Ondrej Moriš 2019-07-23 11:00:13 UTC
Description of problem:

In FIPS mode ssh-keygen -A used to generate all host keys fails because DSA key cannot be generated because it is not allowed in FIPS mode. Unfortunately, keys to be generated after DSA one are not generated as a consequence. 

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

openssh-8.0p1-2.el8

How reproducible:

100% in FIPS mode

Steps to Reproduce:

1. rm /etc/ssh/ssh_host_*
2. ssh-keygen -A
3. ls /etc/ssh/ssh_host_*

Actual results:

(FIPS MODE)

# ssh-keygen -A -m PEM
ssh-keygen: generating new host keys: RSA DSA DSA keys are not allowed in FIPS mode

# ls /etc/ssh/ssh_host_*
/etc/ssh/ssh_host_dsa_key.nxIYddPPw0  /etc/ssh/ssh_host_rsa_key  /etc/ssh/ssh_host_rsa_key.pub

Expected results:

DSA key is skipped and the rest is generated.

Additional info:

(NON_FIPS MODE)

# ssh-keygen -A -m PEM
ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519 

# ls /etc/ssh/ssh_host_*
/etc/ssh/ssh_host_dsa_key      /etc/ssh/ssh_host_ecdsa_key.pub    /etc/ssh/ssh_host_rsa_key
/etc/ssh/ssh_host_dsa_key.pub  /etc/ssh/ssh_host_ed25519_key      /etc/ssh/ssh_host_rsa_key.pub
/etc/ssh/ssh_host_ecdsa_key    /etc/ssh/ssh_host_ed25519_key.pub

Comment 1 Jakub Jelen 2019-07-23 13:02:51 UTC
Created attachment 1592876 [details]
proposed patch

I think this never worked in any previous releases, but I believe it would make sense to fix this.

The attached patch should address the issue.

Comment 8 errata-xmlrpc 2019-11-05 22:41:32 UTC
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.

https://access.redhat.com/errata/RHSA-2019:3702


Note You need to log in before you can comment on or make changes to this bug.