Hide Forgot
Description of problem: SELinux is preventing /sbin/modprobe from 'read' accesses on the directory /etc/modprobe.d. Source Context unconfined_u:unconfined_r:vpnc_t:s0-s0:c0.c1023 Target Context system_u:object_r:modules_conf_t:s0 Target Objects /etc/modprobe.d [ dir ] Source modprobe Source Path /sbin/modprobe Port <Neznámé> Host (removed) Source RPM Packages module-init-tools-3.11.1-2.fc13 Target RPM Packages module-init-tools-3.11.1-2.fc13 Policy RPM selinux-policy-3.9.7-35.fc14 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 2.6.35.11-83.fc14.x86_64 #1 SMP Mon Feb 7 07:06:44 UTC 2011 x86_64 x86_64 Alert Count 11 First Seen Čt 17. březen 2011, 10:43:08 CET Last Seen Po 21. březen 2011, 09:37:53 CET Local ID 7f243232-79e1-413f-be69-9ad6272a147a Raw Audit Messages type=AVC msg=audit(1300696673.243:32): avc: denied { read } for pid=2446 comm="modprobe" name="modprobe.d" dev=md1p1 ino=4098 scontext=unconfined_u:unconfined_r:vpnc_t:s0-s0:c0.c1023 tcontext=system_u:object_r:modules_conf_t:s0 tclass=dir type=SYSCALL msg=audit(1300696673.243:32): arch=x86_64 syscall=open success=no exit=EACCES a0=413698 a1=0 a2=1b6 a3=0 items=0 ppid=2445 pid=2446 auid=500 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts1 ses=1 comm=modprobe exe=/sbin/modprobe subj=unconfined_u:unconfined_r:vpnc_t:s0-s0:c0.c1023 key=(null) Hash: modprobe,vpnc_t,modules_conf_t,dir,read How reproducible: Every first time openconnect is started (after boot). Actual results: Openconnect executes modprobe in vpnc_t and thus fails to read its configuration. However, the module seems to get inserted anyways. Expected results: Transition to insmod_t for modprobe. Additional info: A simple modutils_domtrans_insmod(vpnc_t) fixes the bug.
I think we need a higher level control over this. Perhaps running a version of modutils that could only log the tun module.
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.