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:
When the system is put in fips mode, `ssh -Q key` and `ssh -G example.com | grep key` list algorithms that use the DSS authentication method.
Because DSS in SSH can use only 1024 bit keys, that are considered too weak now, and they are not supported, but are still listed by the above commands

Version-Release number of selected component (if applicable):
openssh-7.4p1-11.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. ssh -Q key | grep dss
2. ssh -G example.com | grep dss
3.

Actual results:
ssh-dss
ssh-dss-cert-v01

hostkeyalgorithms (...),ssh-rsa,ssh-dss
hostbasedkeytypes (...),ssh-rsa,ssh-dss
pubkeyacceptedkeytypes (...),ssh-dss


Expected results:
no dss types listed

Additional info:

We should not use ed25519 keys either in FIPS, which is also listed there. After applying the patch, the output in FIPS looks this:

# ssh -Q key
ssh-rsa
ecdsa-sha2-nistp256
ecdsa-sha2-nistp384
ecdsa-sha2-nistp521
ssh-rsa-cert-v01
ecdsa-sha2-nistp256-cert-v01
ecdsa-sha2-nistp384-cert-v01
ecdsa-sha2-nistp521-cert-v01

# ssh -G example.com | grep dss
(empty)

I have got the patch ready to fix it in 7.4 or later.

no ... we can not remove them from the output of the -Q option, because the keys are technically enabled, but just not used by default.

The -G should certainly not list them.

*** Bug 1459249 has been marked as a duplicate of this bug. ***

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-2018:0980