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.

Bug 1814595

Summary: User safer bcrypt hash function for internal passwords instead of sha1
Product: Red Hat Satellite Reporter: Lukas Zapletal <lzap>
Component: SecurityAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED UPSTREAM QA Contact: Mirek Długosz <mzalewsk>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.7.0CC: ehelms, lzap, mcorr, mhulan, spetrosi, tbrisker
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Previously, password hashing in Satellite used SHA1. As part of this release, new installations of Satellite 6.7 use bcrypt for password hashing. + Users who upgrade from Satellite 6.6 to 6.7 continue to have SHA1 for password hashing until users change their passwords. As part of your upgrade to Satellite, consider enforcing password updates for all users. + To change the bcrypt cost value that you want to use for password hashing, in the Satellite web UI, navigate to *Administer* > *Settings*, click the *Authentication* tab, and edit the *BCrypt password cost* setting. + Changes to the bcrypt cost value are implemented after the next password change. Note that while higher values are safer, higher bcrypt cost values have a performance impact on API and UI logins.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-18 10:52:53 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:
Embargoed:

Description Lukas Zapletal 2020-03-18 10:50:54 UTC 
Implement bcrypt and replace our SHA1 hashing algo with it. Make the bcrypt cost a configurable option in Administer - Settings and during initial DB seed calculate a good starting value.

Note: This BZ was created as a tracker for already closed upstream bug for our docs team.