Bug 246666

Summary:	SELinux is preventing /usr/sbin/wpa_supplicant (NetworkManager_t) "execute_no_trans" to /usr/sbin/wpa_supplicant (NetworkManager_exec_t).
Product:	[Fedora] Fedora	Reporter:	Bill Nottingham <notting>
Component:	selinux-policy	Assignee:	Daniel Walsh <dwalsh>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	rawhide	CC:	adrielchagay, rvokal
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	Current	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-08-22 14:15:23 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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