Description of problem: I'm still seeing these 2 alsactl avc-s with Fedora-19 after upgrading to selinux-policy-3.12.1-31.fc19.noarch. After installing this version I deleted all alerts in sealert, rebooted and logged into gnome-3.8, and ran sealert again . After this there were 2 alsactl avc-s in selalert, this one and the one in my other bug report. SELinux is preventing /usr/sbin/alsactl from 'write' accesses on the directory /run. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that alsactl should be allowed write access on the run 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 alsactl /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:alsa_t:s0 Target Context system_u:object_r:var_run_t:s0 Target Objects /run [ dir ] Source alsactl Source Path /usr/sbin/alsactl Port <Unknown> Host (removed) Source RPM Packages alsa-utils-1.0.27-2.fc19.x86_64 Target RPM Packages filesystem-3.2-9.fc19.x86_64 Policy RPM selinux-policy-3.12.1-31.fc19.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.9.0-0.rc6.git2.3.fc19.x86_64 #1 SMP Mon Apr 15 20:34:53 UTC 2013 x86_64 x86_64 Alert Count 1 First Seen 2013-04-19 13:33:37 CEST Last Seen 2013-04-19 13:33:37 CEST Local ID 6172c5f2-0736-4439-b58e-a3a49f0e320d Raw Audit Messages type=AVC msg=audit(1366371217.80:7): avc: denied { write } for pid=553 comm="alsactl" name="/" dev="tmpfs" ino=6205 scontext=system_u:system_r:alsa_t:s0 tcontext=system_u:object_r:var_run_t:s0 tclass=dir type=SYSCALL msg=audit(1366371217.80:7): arch=x86_64 syscall=open success=no exit=EACCES a0=4117e8 a1=c1 a2=180 a3=0 items=0 ppid=1 pid=553 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=4294967295 tty=(none) comm=alsactl exe=/usr/sbin/alsactl subj=system_u:system_r:alsa_t:s0 key=(null) Hash: alsactl,alsa_t,var_run_t,dir,write audit2allow #============= alsa_t ============== allow alsa_t var_run_t:dir write; audit2allow -R require { type alsa_t; } #============= alsa_t ============== files_rw_pid_dirs(alsa_t) Additional info: hashmarkername: setroubleshoot kernel: 3.9.0-0.rc6.git2.3.fc19.x86_64 type: libreport
Fixed in selinux-policy-3.12.1-34.fc19.noarch THis locks good in 34
selinux-policy-3.12.1-39.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/selinux-policy-3.12.1-39.fc19
Package selinux-policy-3.12.1-39.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing selinux-policy-3.12.1-39.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-7338/selinux-policy-3.12.1-39.fc19 then log in and leave karma (feedback).
Package selinux-policy-3.12.1-40.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing selinux-policy-3.12.1-40.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-7338/selinux-policy-3.12.1-40.fc19 then log in and leave karma (feedback).
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.