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.
Bug 1721419 - SSH key cannot be added when FIPS enabled
Summary: SSH key cannot be added when FIPS enabled
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Users & Roles
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.8.0
Assignee: Leos Stejskal
QA Contact: Radovan Drazny
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-18 09:16 UTC by Jan Jansky
Modified: 2023-12-15 16:34 UTC (History)
6 users (show)

Fixed In Version: foreman-2.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 12:58:39 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 28861 0 Normal Closed SSH key cannot be added when FIPS enabled 2021-01-19 15:35:36 UTC
Red Hat Knowledge Base (Solution) 4293921 0 Troubleshoot None FIPS enabled Red Hat Satellite 6 is throwing 500 internal server error while adding ssh key to users. 2019-07-19 16:10:41 UTC
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 12:58:53 UTC

Description Jan Jansky 2019-06-18 09:16:10 UTC 
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:
Comment 8 Marek Hulan 2019-11-21 11:09:08 UTC 
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.
Comment 9 Leos Stejskal 2020-01-27 11:10:52 UTC 
Created redmine issue https://projects.theforeman.org/issues/28861 from this bug
Comment 10 Bryan Kearney 2020-02-05 11:04:06 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28861 has been resolved.
Comment 11 Radovan Drazny 2020-09-22 11:22:14 UTC 
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.
Comment 14 errata-xmlrpc 2020-10-27 12:58:39 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 (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
Note You need to log in before you can comment on or make changes to this bug.