Description of problem: SELinux is preventing charon from 'getattr' accesses on the chr_file /dev/tpmrm0. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that charon should be allowed getattr access on the tpmrm0 chr_file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # ausearch -c 'charon' --raw | audit2allow -M my-charon # semodule -X 300 -i my-charon.pp Additional Information: Source Context system_u:system_r:ipsec_t:s0 Target Context system_u:object_r:tpm_device_t:s0 Target Objects /dev/tpmrm0 [ chr_file ] Source charon Source Path charon Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-36.8-2.fc36.noarch Local Policy RPM selinux-policy-targeted-36.8-2.fc36.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 5.17.6-300.fc36.x86_64 #1 SMP PREEMPT Mon May 9 15:47:11 UTC 2022 x86_64 x86_64 Alert Count 1 First Seen 2022-05-16 22:29:21 EEST Last Seen 2022-05-16 22:29:21 EEST Local ID f022d832-e285-4773-a980-72599bbe2ef6 Raw Audit Messages type=AVC msg=audit(1652729361.214:334): avc: denied { getattr } for pid=1642 comm="charon" path="/dev/tpmrm0" dev="devtmpfs" ino=135 scontext=system_u:system_r:ipsec_t:s0 tcontext=system_u:object_r:tpm_device_t:s0 tclass=chr_file permissive=0 Hash: charon,ipsec_t,tpm_device_t,chr_file,getattr Version-Release number of selected component: selinux-policy-targeted-36.8-2.fc36.noarch Additional info: component: selinux-policy reporter: libreport-2.17.1 hashmarkername: setroubleshoot kernel: 5.17.6-300.fc36.x86_64 type: libreport Potential duplicate: bug 2018827
Hi, Do you happen to know at which moment this denial appears?
*** Bug 2018827 has been marked as a duplicate of this bug. ***
*** Bug 2092249 has been marked as a duplicate of this bug. ***
*** Bug 2026328 has been marked as a duplicate of this bug. ***
Mai Ling, Can you try your scenario in SELinux permissive mode to gather all subsequent denials? # setenforce 0 <reproduce> # setenforce 1 # ausearch -i -m avc,user_avc,selinux_err,user_selinux_err -ts today
FEDORA-2022-096f7730be has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-096f7730be
FEDORA-2022-096f7730be has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-096f7730be` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-096f7730be See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-096f7730be has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days