Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
DescriptionJimmie Mayfield
2021-06-13 04:03:10 UTC
Description of problem:
On CentOS 8 Stream, SELinux 'unix_chkpwd' triggers an SELinux violation
sealert -l f26706db-2c08-4ee4-b0cf-be5534e68597
SELinux is preventing /usr/sbin/unix_chkpwd from getattr access on the filesystem /proc.
...
Raw Audit Messages
type=AVC msg=audit(1623556801.295:290): avc: denied { getattr } for pid=10311 comm="unix_chkpwd" name="/" dev="proc" ino=1 scontext=system_u:system_r:chkpwd_t:s0-s0:c0.c1023 tcontext=system_u:object_r:proc_t:s0 tclass=filesystem permissive=0
...
type=SYSCALL msg=audit(1623556801.295:290): arch=x86_64 syscall=fstatfs success=no exit=EACCES a0=3 a1=7fff617eba70 a2=0 a3=0 items=0 ppid=10301 pid=10311 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=unix_chkpwd exe=/usr/sbin/unix_chkpwd subj=system_u:system_r:chkpwd_t:s0-s0:c0.c1023 key=(null)
Version-Release number of selected component (if applicable):
OS: CentOS 8 Stream with the most recent updates
pam-1.3.1-15.el8.x86_64
selinux-policy-3.14.3-68.el8.noarch
As far as SELinux policies and PAM configuration are concerned, this machine appears to be using the package default configurations. No local customizations have been made to SELinux or PAM config.
How reproducible:
This occurs every time someone logs into the machine
Steps to Reproduce:
1. Log into the machine
2.
3.
Actual results:
Successful login is accompanied by a series of messages written to the journal indicating unix_chkpwd has triggered an SELinux action
Expected results:
Near as I can tell, this machine has no customized local policies and is using the default PAM config files. I would expect a default installation to not trigger SELinux actions.
Additional info:
Thank you for the confirmation, resolution for this bz should be a part of RHEL 8.5, it is a (non-obvious) dup of bz#1967125.
*** This bug has been marked as a duplicate of bug 1967125 ***
Description of problem: On CentOS 8 Stream, SELinux 'unix_chkpwd' triggers an SELinux violation sealert -l f26706db-2c08-4ee4-b0cf-be5534e68597 SELinux is preventing /usr/sbin/unix_chkpwd from getattr access on the filesystem /proc. ... Raw Audit Messages type=AVC msg=audit(1623556801.295:290): avc: denied { getattr } for pid=10311 comm="unix_chkpwd" name="/" dev="proc" ino=1 scontext=system_u:system_r:chkpwd_t:s0-s0:c0.c1023 tcontext=system_u:object_r:proc_t:s0 tclass=filesystem permissive=0 ... type=SYSCALL msg=audit(1623556801.295:290): arch=x86_64 syscall=fstatfs success=no exit=EACCES a0=3 a1=7fff617eba70 a2=0 a3=0 items=0 ppid=10301 pid=10311 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=unix_chkpwd exe=/usr/sbin/unix_chkpwd subj=system_u:system_r:chkpwd_t:s0-s0:c0.c1023 key=(null) Version-Release number of selected component (if applicable): OS: CentOS 8 Stream with the most recent updates pam-1.3.1-15.el8.x86_64 selinux-policy-3.14.3-68.el8.noarch As far as SELinux policies and PAM configuration are concerned, this machine appears to be using the package default configurations. No local customizations have been made to SELinux or PAM config. How reproducible: This occurs every time someone logs into the machine Steps to Reproduce: 1. Log into the machine 2. 3. Actual results: Successful login is accompanied by a series of messages written to the journal indicating unix_chkpwd has triggered an SELinux action Expected results: Near as I can tell, this machine has no customized local policies and is using the default PAM config files. I would expect a default installation to not trigger SELinux actions. Additional info: