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:

Satellite uses bcrypt for password hashing, introduced in Satellite version 6.7 link[1], and bcrypt is based on the Blowfish cipher and blowfish is not fips compliant, so the STIG scanner is raising an exception that the database appears to use non-FIPS compliant encryption.




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

6.9


Expected results:

Replace bcrypt hash function with (FIPS-approved / NIST recommended) encryption algorithm for internal passwords in the Satellite.


Additional info:

[1]Bug 1814595 - User safer bcrypt hash function for internal passwords instead of sha1
https://bugzilla.redhat.com/show_bug.cgi?id=1814595

Upstream bug assigned to lzap

Upstream bug assigned to lzap

Upstream bug assigned to lzap

Upstream bug assigned to lzap

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/32572 has been resolved.

verified on the satellite 6.11 with snap 16 working as expected.

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 (Moderate: Satellite 6.11 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-2022:5498