systemd or selinux problem? CAP_SYS_MODULE/CAP_NET_ADMIN

[Ian Malone]

On 20 November 2011 00:09, Ian Malone <ibmalone at gmail.com> wrote:
> On 19 November 2011 18:38, Deron Meranda <deron.meranda at gmail.com> wrote:
>> On Sat, Nov 19, 2011 at 9:42 AM, Ian Malone <ibmalone at gmail.com> wrote:
>>> I've got quite a few of these during boot, anyone know what might be the cause?
>>>
>>> Loading kernel module for a network device with CAP_SYS_MODULE (deprecated).
>>> Use CAP_NET_ADMIN and alias X instead.
>>>
>>> Where X includes netdev-snd_ice1724, netdev-snd_ac97_codec, netdev-fat,
>>> netdev-vfat, netdev-bluetooth, netdev-nf_conntrack and others. Think
>>> they may all be netdev-. I've tried an autorelabel in case it's a
>>> labelling issue.
>>
>> This sounds like neither a systemd nor an SELinux issue.  Are you
>> seeing anything more specific, like an AVC error?
>>
>
> No I'm not, two unrelated sealerts (gnome-session-check-accel,
> /bin/mailx). I know there's a systemd unit (or appears to be) to load
> kernel modules, I was wondering if this was responsible for attempting
> to load these with the wrong context.
>
>> Anyway the CAP_* symbols refer to the kernel "capabilities" (do a man
>> capabilities). These are kernel-level security features, but unrelated
>> to SELinux.
>>
>
> Interesting, thanks.

If anyone else encounters this or a similar issue it was caused by a
broken udev rule. To work around this bug
https://bugzilla.redhat.com/show_bug.cgi?id=753648 I had the following
rule, but with a spurious newline:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="rt2500pci", KERNEL=="wlan*",
RUN="/sbin/iw $name set power_save off"

rather than
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="rt2500pci",
KERNEL=="wlan*", RUN="/sbin/iw $name set power_save off"

-- 
imalone