pull request: wireless-2.6 2008-11-25
apologize for not sending the original post (accidentally removed it);
from the post:
http://lkml.org/lkml/2008/11/25/353
I take it this is the reason for the avc's that are being created, and always denied: <example>
-- [ 26.659175] type=1400 audit(1227658649.652:3): avc: denied
{ sys_module } for pid=2631 comm="wpa_supplicant" capability=16 scontext=system_u:system_r:system_dbusd_t:s0 tcontext=system_u:system_r:system_dbusd_t:s0 tclass=capability
[ 26.659351] type=1300 audit(1227658649.652:3): arch=40000003
syscall=54 success=no exit=-19 a0=9 a1=8933 a2=bfb6ff9c a3=bfb6ff9c items=0 ppid=1 pid=2631 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="wpa_supplicant" exe="/sbin/wpa_supplicant" subj=system_u:system_r:system_dbusd_t:s0 key=(null)
[ 30.131444] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 30.140774] input: justinmattocks mouse #1 as /class/input/input10
[ 30.194328] generic-bluetooth 0005:0000:0000.0004: input: BLUETOOTH
HID v0.00 Mouse [justinmattocks mouse #1] on 00:17:F2:B4:BC:F5
[ 33.361691] [drm] Setting GART location based on new memory map
[ 33.363216] [drm] Loading R500 Microcode
[ 33.363295] [drm] Num pipes: 1
[ 33.363309] [drm] writeback test succeeded in 1 usecs
[ 84.658454] wlan0: authenticate with AP 00:1e:2a:00:67:f0
[ 84.664222] wlan0: authenticated
[ 84.664230] wlan0: associate with AP 00:1e:2a:00:67:f0
[ 84.666704] wlan0: RX AssocResp from 00:1e:2a:00:67:f0 (capab=0x431
status=0 aid=34)
[ 84.666710] wlan0: associated
[ 92.657555] type=1400 audit(1227658715.650:4): avc: denied
{ sys_admin } for pid=3042 comm="mount" capability=21
scontext=system_u:system_r:system_dbusd_t:s0
tcontext=system_u:system_r:system_dbusd_t:s0 tclass=capability
[ 92.657594] type=1300 audit(1227658715.650:4): arch=40000003syscall=21 success=no exit=-1 a0=8061818 a1=8061828 a2=805a521 a3=c0ed1000 items=0 ppid=3033 pid=3042 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="mount" exe="/bin/mount" subj=system_u:system_r:system_dbusd_t:s0 key=(null)
[ 92.661764] type=1400 audit(1227658715.660:5): avc: denied
{ sys_admin } for pid=3044 comm="mount" capability=21
scontext=system_u:system_r:system_dbusd_t:s0
tcontext=system_u:system_r:system_dbusd_t:s0 tclass=capability
[ 92.661820] type=1300 audit(1227658715.660:5): arch=40000003syscall=21 success=no exit=-1 a0=8061818 a1=8061828 a2=805a521 a3=c0ed1000 items=0 ppid=3033 pid=3044 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="mount" exe="/bin/mount" subj=system_u:system_r:system_dbusd_t:s0 key=(null)
allow rules are as is:
#============= system_dbusd_t ==============
allow system_dbusd_t self:capability { sys_module sys_admin };
I do have debug enabled for ath9k;
I'll look at the policy(once the wireless is committed) to see if this was the resulting... and/or happening.
regards;
Justin P. Mattock <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 65 lines · Justin P. Mattock
apologize for not sending the original post (accidentally removed it);
from the post:
http://lkml.org/lkml/2008/11/25/353
I take it this is the reason for the avc's that are being created, and always denied: <example>-- [ 26.659175] type=1400 audit(1227658649.652:3): avc: denied
{sys_module} for pid=2631 comm="wpa_supplicant" capability=16 scontext=system_u:system_r:system_dbusd_t:s0 tcontext=system_u:system_r:system_dbusd_t:s0 tclass=capability[ 26.659351] type=1300 audit(1227658649.652:3): arch=40000003syscall=54 success=no exit=-19 a0=9 a1=8933 a2=bfb6ff9c a3=bfb6ff9c items=0 ppid=1 pid=2631 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="wpa_supplicant" exe="/sbin/wpa_supplicant" subj=system_u:system_r:system_dbusd_t:s0 key=(null)
[ 30.131444] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 30.140774] input: justinmattocks mouse #1 as /class/input/input10 [ 30.194328] generic-bluetooth 0005:0000:0000.0004: input: BLUETOOTH HID v0.00 Mouse [justinmattocks mouse #1] on 00:17:F2:B4:BC:F5 [ 33.361691] [drm] Setting GART location based on new memory map [ 33.363216] [drm] Loading R500 Microcode [ 33.363295] [drm] Num pipes: 1 [ 33.363309] [drm] writeback test succeeded in 1 usecs [ 84.658454] wlan0: authenticate with AP 00:1e:2a:00:67:f0 [ 84.664222] wlan0: authenticated [ 84.664230] wlan0: associate with AP 00:1e:2a:00:67:f0 [ 84.666704] wlan0: RX AssocResp from 00:1e:2a:00:67:f0 (capab=0x431 status=0 aid=34) [ 84.666710] wlan0: associated [ 92.657555] type=1400 audit(1227658715.650:4): avc: denied { sys_admin } for pid=3042 comm="mount" capability=21 scontext=system_u:system_r:system_dbusd_t:s0 tcontext=system_u:system_r:system_dbusd_t:s0 tclass=capability [ 92.657594] type=1300 audit(1227658715.650:4): arch=40000003syscall=21 success=no exit=-1 a0=8061818 a1=8061828 a2=805a521 a3=c0ed1000 items=0 ppid=3033 pid=3042 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="mount" exe="/bin/mount" subj=system_u:system_r:system_dbusd_t:s0 key=(null)
[ 92.661764] type=1400 audit(1227658715.660:5): avc: denied { sys_admin } for pid=3044 comm="mount" capability=21 scontext=system_u:system_r:system_dbusd_t:s0 tcontext=system_u:system_r:system_dbusd_t:s0 tclass=capability [ 92.661820] type=1300 audit(1227658715.660:5): arch=40000003syscall=21 success=no exit=-1 a0=8061818 a1=8061828 a2=805a521 a3=c0ed1000 items=0 ppid=3033 pid=3044 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="mount" exe="/bin/mount" subj=system_u:system_r:system_dbusd_t:s0 key=(null)
allow rules are as is:
#=============
system_dbusd_t==============
allowsystem_dbusd_tself:capability {sys_modulesys_admin};I do have debug enabled for ath9k;
I'll look at the policy(once the wireless is committed) to see if this was the resulting... and/or happening.regards;
Quoted 6 lines
Justin P. Mattock <[email protected]>
_______________________________________________
refpolicy mailing list
refpolicy at oss.tresys.com
http://oss.tresys.com/mailman/listinfo/refpolicy
You want to have a transition defined between dbus and wpa_supplicant. In Fedora wpa_supplicant is labeled NetworkManager_exec_t and system_dbusd_t transitions to NetworkManager_r when executing it.
In the future dbus is going to start a lot of System Services so each needs a transition rule or else dbus will approacue an unconfined domain. -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkkv6YsACgkQrlYvE4MpobM/EQCgoJoAjYfG2Ei1/DiWbgEnMdrC lK4AoLlgOcz+nhm5RwVlyT5DAbslMtqQ
=Rb86
-----END PGP SIGNATURE-----