Bug 1814595
| Summary: | User safer bcrypt hash function for internal passwords instead of sha1 | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Lukas Zapletal <lzap> |
| Component: | Security | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED UPSTREAM | QA Contact: | Mirek Długosz <mzalewsk> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.7.0 | CC: | 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
|