Bug 246666 - SELinux is preventing /usr/sbin/wpa_supplicant (NetworkManager_t) "execute_no_trans" to /usr/sbin/wpa_supplicant (NetworkManager_exec_t).
Summary: SELinux is preventing /usr/sbin/wpa_supplicant (NetworkManager_t) "execute_no...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-07-03 19:15 UTC by Bill Nottingham
Modified: 2023-04-15 03:14 UTC (History)
2 users (show)

Fixed In Version: Current
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-08-22 14:15:23 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Bill Nottingham 2007-07-03 19:15:49 UTC 
Description of problem:

SSIA

Version-Release number of selected component (if applicable):

selinux-policy-3.0.1-6.fc8
NetworkManager-0.6.5-7.fc8
Comment 1 Daniel Walsh 2007-07-03 19:25:37 UTC 
That rule should be allowed,  can you attach the avc message?
Comment 2 Bill Nottingham 2007-07-03 19:59:16 UTC 
type=AVC msg=audit(1183489825.865:86): avc:  denied  { execute_no_trans } for 
pid=3795 comm=
"NetworkManager" name="wpa_supplicant" dev=sda2 ino=5639713
scontext=system_u:system_r:Networ
kManager_t:s0 tcontext=system_u:object_r:NetworkManager_exec_t:s0 tclass=file
Comment 3 Daniel Walsh 2007-07-03 21:09:30 UTC 
selinux-policy-3.0.2-1.fc8  policy has this as allowed.

 audit2why < /tmp/t
type=AVC msg=audit(1183489825.865:86): avc:  denied  { execute_no_trans } for
pid=3795 comm="NetworkManager" name="wpa_supplicant" dev=sda2 ino=5639713
scontext=system_u:system_r:NetworkManager_t:s0
tcontext=system_u:object_r:NetworkManager_exec_t:s0 tclass=file
        Was caused by:
                Unknown - would be allowed by active policy
                Possible mismatch between this policy and the one under which
the audit message was generated.
                Possible mismatch between current in-memory boolean settings vs.
permanent ones.


So I guess it is fixed by tonights rawhide, although I don;t believe anything
has changed.
Comment 4 Daniel Walsh 2007-08-22 14:15:23 UTC 
Should be fixed in the current release
Note You need to log in before you can comment on or make changes to this bug.