From: justinmattock@gmail.com (Justin P. Mattock) Date: Thu, 18 Dec 2008 09:43:35 -0800 Subject: [refpolicy] ath9k capability=16 won't compile into policy In-Reply-To: <494A7E0D.6050200@redhat.com> References: <494A7E0D.6050200@redhat.com> Message-ID: <494A8BC7.7000407@gmail.com> To: refpolicy@oss.tresys.com List-Id: refpolicy.oss.tresys.com Daniel J Walsh wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Justin Mattock wrote: > >> I'm not too sure if I should post this with SELinux, >> refpolicy, or kernel.org,(or even wpasupplicant); >> so I decided to do all to the best of my knowledge. >> when using the ath9k module with the latest git >> kernel(or atleast a few days old); and the latest refpolicy (svn) >> I'm seeing this avc denial show up: >> >> Dec 16 12:33:32 name kernel: [ 20.415785] type=1400 >> audit(1229459612.411:3): avc: denied { sys_module } for pid=2510 >> 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 >> Dec 16 12:33:32 name kernel: [ 20.428494] type=1300 >> audit(1229459612.411:3): arch=40000003 syscall=54 success=no exit=-19 >> a0=9 a1=8933 a2=bfadd94c a3=bfadd94c items=0 ppid=1 pid=2510 >> 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) >> >> the allow rule is:(with ath9k module) >> allow system_dbusd_t self:capability sys_module; >> which in turn will be rejected by checkpolicy >> (capability 16) >> when compiling the policy. >> >> If I use the madwifi module the avc is similar but produces >> allow system_dbusd_t self:capability { sys_admin } >> (capability 12) >> and will be accepted by checkpolicy. >> >> As for setup I'm using NetworkManager from >> intrepid as well as wpasupplicant >> >> Any info would be appreciated so I can test this module out >> and feel better knowing the module is not being denied in any >> way, that might cause a false positive, or some other weirdness. >> >> >> regards; >> > We label wpa_supplicant as NetworkManager_exec_t and have dbus > transition to this domain. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org > > iEYEARECAAYFAklKfg0ACgkQrlYvE4MpobPltQCfbcRlboJohHcUaUaASFMbj1LK > /9AAoNPuDJuPv3B4tpikLzsjUPYCUe4I > =Nozo > -----END PGP SIGNATURE----- > > Cool thanks for the info. I just have to figure out how to get the machine to do that. i.g. through dispatcher.d or network/interfaces. one thing that I'm noticing is ubuntu's version of NetworkManager only has two plugins(01ifupdown,keyfile); I'll try loading another version and see if the other plugins is what I'm missing to have dbusd transition correctly. regards; Justin P. Mattock