Hide Forgot
SELinux is preventing /lib/systemd/systemd-tmpfiles from 'read' accesses on the directory tr. ***** Plugin file (36.8 confidence) suggests ******************************* If you think this is caused by a badly mislabeled machine. Then you need to fully relabel. Do touch /.autorelabel; reboot ***** Plugin file (36.8 confidence) suggests ******************************* If you think this is caused by a badly mislabeled machine. Then you need to fully relabel. Do touch /.autorelabel; reboot ***** Plugin catchall_labels (23.2 confidence) suggests ******************** If you want to allow systemd-tmpfiles to have read access on the tr directory Then you need to change the label on tr Do # semanage fcontext -a -t FILE_TYPE 'tr' where FILE_TYPE is one of the following: cert_t, etc_t, man_t, tmp_t, textrel_shlib_t, device_t, locale_t, var_auth_t, lockfile, etc_t, pidfile, tmpfile, lost_found_t, var_run_t, systemd_tmpfiles_t, net_conf_t, sysctl_crypto_t, abrt_t, lib_t, root_t, usr_t, device_t, cert_t, var_lib_t, net_conf_t, nscd_var_run_t. Then execute: restorecon -v 'tr' ***** Plugin catchall (5.04 confidence) suggests *************************** If you believe that systemd-tmpfiles should be allowed read access on the tr directory 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: # grep systemd-tmpfile /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:systemd_tmpfiles_t:s0 Target Context system_u:object_r:file_t:s0 Target Objects tr [ dir ] Source systemd-tmpfile Source Path /lib/systemd/systemd-tmpfiles Port <Unknown> Host (removed) Source RPM Packages systemd-17-2.fc15 Target RPM Packages Policy RPM selinux-policy-3.9.13-9.fc15 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 2.6.38-0.rc4.git0.1.fc15.x86_64 #1 SMP Tue Feb 8 01:57:21 UTC 2011 x86_64 x86_64 Alert Count 1 First Seen Sat 12 Feb 2011 09:10:27 PM EST Last Seen Sat 12 Feb 2011 09:10:27 PM EST Local ID 210ca4e9-936e-4823-8544-97c3e61c2344 Raw Audit Messages type=AVC msg=audit(1297563027.453:81): avc: denied { read } for pid=2390 comm="systemd-tmpfile" name="tr" dev=dm-0 ino=86214 scontext=system_u:system_r:systemd_tmpfiles_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir type=SYSCALL msg=audit(1297563027.453:81): arch=x86_64 syscall=openat success=yes exit=EIO a0=4 a1=e313ab a2=b0800 a3=0 items=0 ppid=1 pid=2390 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=systemd-tmpfile exe=/lib/systemd/systemd-tmpfiles subj=system_u:system_r:systemd_tmpfiles_t:s0 key=(null) Hash: systemd-tmpfile,systemd_tmpfiles_t,file_t,dir,read audit2allow #============= systemd_tmpfiles_t ============== allow systemd_tmpfiles_t file_t:dir read; audit2allow -R #============= systemd_tmpfiles_t ============== allow systemd_tmpfiles_t file_t:dir read;
What is and where is "tr" located. You will need to run restorecon on it.
(In reply to comment #1) > What is and where is "tr" located. You will need to run restorecon on it. It happened running a F15TC1 live image and I don't know what is or where is "tr" located. I'm not completely sure, but I think this avc appears right after login, I'll check tonight.
This is a bug in live image or in the tool livecdtools which did not put the correct labels on this livecd
SELinux is preventing /bin/systemd-tmpfiles from read access on the directory keyring-Jg3p2W. ***** Plugin file (36.8 confidence) suggests ******************************* If you think this is caused by a badly mislabeled machine. Then you need to fully relabel. Do touch /.autorelabel; reboot ***** Plugin file (36.8 confidence) suggests ******************************* If you think this is caused by a badly mislabeled machine. Then you need to fully relabel. Do touch /.autorelabel; reboot ***** Plugin catchall_labels (23.2 confidence) suggests ******************** If you want to allow systemd-tmpfiles to have read access on the keyring-Jg3p2W directory Then you need to change the label on keyring-Jg3p2W Do # semanage fcontext -a -t FILE_TYPE 'keyring-Jg3p2W' where FILE_TYPE is one of the following: rpm_var_cache_t, faillog_t, proc_net_t, var_run_t, rpm_var_lib_t, net_conf_t, home_root_t, cert_t, man_t, tmp_t, user_home_dir_t, sysctl_crypto_t, device_t, locale_t, var_auth_t, etc_t, lockfile, pidfile, tmpfile, tmpfs_t, abrt_t, lib_t, root_t, usr_t, lost_found_t, device_t, etc_t, systemd_tmpfiles_t, sandbox_file_t, textrel_shlib_t, user_home_type, net_conf_t, nscd_var_run_t, cert_t, var_lib_t. Then execute: restorecon -v 'keyring-Jg3p2W' ***** Plugin catchall (5.04 confidence) suggests *************************** If you believe that systemd-tmpfiles should be allowed read access on the keyring-Jg3p2W directory 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: # grep systemd-tmpfile /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:systemd_tmpfiles_t:s0 Target Context system_u:object_r:file_t:s0 Target Objects keyring-Jg3p2W [ dir ] Source systemd-tmpfile Source Path /bin/systemd-tmpfiles Port <Unknown> Host (removed) Source RPM Packages systemd-units-26-5.fc15 Target RPM Packages Policy RPM selinux-policy-3.9.16-30.fc15 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux hicham-laptop 2.6.38.8-32.fc15.i686 #1 SMP Mon Jun 13 20:01:50 UTC 2011 i686 i686 Alert Count 11 First Seen Fri 24 Jun 2011 02:30:03 AM WEST Last Seen Mon 27 Jun 2011 11:16:07 PM WEST Local ID 963eac1d-2a66-4905-90e9-0b3f1cdf077e Raw Audit Messages type=AVC msg=audit(1309212967.381:35): avc: denied { read } for pid=1363 comm="systemd-tmpfile" name="keyring-Jg3p2W" dev=sda5 ino=107288 scontext=system_u:system_r:systemd_tmpfiles_t:s0 tcontext=system_u:object_r:file_t:s0 tclass=dir type=SYSCALL msg=audit(1309212967.381:35): arch=i386 syscall=openat success=yes exit=ENXIO a0=4 a1=8ade88b a2=b8800 a3=0 items=0 ppid=1 pid=1363 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=systemd-tmpfile exe=/bin/systemd-tmpfiles subj=system_u:system_r:systemd_tmpfiles_t:s0 key=(null) Hash: systemd-tmpfile,systemd_tmpfiles_t,file_t,dir,read audit2allow #============= systemd_tmpfiles_t ============== allow systemd_tmpfiles_t file_t:dir read; audit2allow -R #============= systemd_tmpfiles_t ============== allow systemd_tmpfiles_t file_t:dir read; keyring-Jg3p2W directory is in tmp running restorecon on it didn't fix the issue
hicham@hicham-laptop ~ $ ls -Z /tmp/keyring-Jg3p2W srwxr-xr-x. hicham hicham system_u:object_r:file_t:s0 control
Is this still on a livecd?
fixed in selinux-policy-3.9.16-31.fc15
(In reply to comment #6) > Is this still on a livecd? No, it is on an updated system
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.