Bug 1732424

Summary: ssh-keygen -A fails in FIPS mode because of DSA key
Product: Red Hat Enterprise Linux 8 Reporter: Ondrej Moriš <omoris>
Component: opensshAssignee: Jakub Jelen <jjelen>
Status: CLOSED ERRATA QA Contact: Ivan Nikolchev <inikolch>
Severity: low Docs Contact:
Priority: low    
Version: 8.1CC: inikolch, tmraz
Target Milestone: rcKeywords: Triaged
Target Release: 8.0   
Hardware: All   
OS: Linux   
Fixed In Version: openssh-8.0p1-3.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 22:41:32 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:
Description Flags
proposed patch none

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):


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:


# 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:


# 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.