Add a warning about hashing algorithms#14231
Merged
Mab879 merged 1 commit intoComplianceAsCode:masterfrom Dec 11, 2025
Merged
Conversation
CIS Benchmarks for all RHEL versions (8, 9, 10) permit using both sha512 and yescrypt algorithms for password hashing. However, users shouldn't mix them to use both at once. Users should choose one of them and use it consistently. Therefore, our rules need to specify a single specific algortihm. Users can switch to the other one in their profiles by changing the value of the `var_password_hashing_algorithm_pam` variable in tailoring files. We will add a warning to these rules to explain users this situation. Resolves: https://issues.redhat.com/browse/OPENSCAP-6100
|
@jan-cerny: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Mab879
approved these changes
Dec 11, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CIS Benchmarks for all RHEL versions (8, 9, 10) permit using both sha512 and yescrypt algorithms for password hashing. However, users shouldn't mix them to use both at once. Users should choose one of them and use it consistently. Therefore, our rules need to specify a single specific algortihm. Users can switch to the other one in their profiles by changing the value of the
var_password_hashing_algorithm_pamvariable in tailoring files. We will add a warning to these rules to explain users this situation.Resolves: https://issues.redhat.com/browse/OPENSCAP-6100