Update pam_rhel.yml - #962
Open
je4yfc wants to merge 1 commit into
Open
Conversation
This fixes dev-sec#922.
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
1 participant
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.
This fixes #922.
The current RHEL PAM tasks create
system-auth-localandpassword-auth-localasroot:rootwith mode0640. that makes the files readable only by root, since there is no standardpamgroup that unprivileged PAM consumers belong to. That breaks applications such asswaylockandxscreensaver, which call into PAM as the logged-in user and need to read the relevant service configuration.I checked the likely benchmark lineage for this setup. The RHEL 7 STIG guidance explains the use of
system-auth-localandpassword-auth-localto preventauthconfigfrom overwriting hardened PAM configuration, but I could not find a requirement that these files be unreadable by ordinary users. Current ComplianceAsCode-generated RHEL 9 content also uses0644for/etc/pam.d/password-auth.PAM configuration files generally do not contain secrets. Their integrity matters, but that remains protected by
root:rootownership and the absence of group or world write permissions. If a PAM module requires a secret, that secret should live in a separate root-only file rather than relying on the entire PAM policy being unreadable.