Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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 FIPS is enabled and customer will try to add SSH key for user, 500 internal server error appear
Version-Release number of selected component (if applicable):
satellite-6.5.0-11.el7sat.noarch
How reproducible: Always
Steps to Reproduce:
1. Create new user
2. generate new key
3. Edit user -> SSH Keys -> Add SSH Keys
4. Fill new SSH key
Actual results:
500 Internal server error
Expected results:
Key added
Additional info:
SSHKey.generate defaults to md5 for fingerprint which is unavailable in FIPS enabled system. We don't use ActiveSupport::Digest.hexdigest for generating the hash for the key, but use SSHKey.generate directly, hence it was missed in FIPS enabling PR. We can use SSHKey.sha1_generate instead to enforce safe hash function.
Tested on Satellite 6.8 Snap 16 using the reproducer from the initial report. SSH key for a new user has been added successfully, the fingerprint generated is SHA256 based and correct. Adding both from WebUI and hammer works.
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 (Important: Satellite 6.8 release), 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-2020:4366