sysfs vs. d80211 configuration

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hey,

In my seemingly never-ending quest to actually use the d80211 stack for something useful I just wanted to write a small setuid tool that:
* creates and opens a new monitor interface
* drops priviledges
* ... does things with received frames ... (not interesting for this discussion)
* removes new monitor interface

So I figured I'd just keep an fd open to /sys/class/net/mymonitorinterface/remove_iface to which I could write the interfaces name after I was done with it. However, when writing to that fd I got -EACCESS because it checks for CAP_NET_ADMIN.

That seems to make sense. However, it also means that I can simply not write the tool that way, it can't drop priviledges. Of course it could re-exec itself with a special parameter to tell it to remove the interface, but that'd allow anyone to use it to remove any interface. Not good either.

Hence, it seems that in order to properly solve this I should simply add a new sysfs "remove" property for each d80211 virtual interface that triggers a removal whenever anything is written to it. And it should not have a check for CAP_NET_ADMIN so I can use it after dropping priviledges. Sounds great, right? So why isn't there a patch attached to this mail?

Well, it isn't too great. See, if you think about it again, removing an interface *should* require CAP_NET_ADMIN. But if I want to enable above use-case, then I have to check for CAP_NET_ADMIN when *opening* the sysfs attribute file, not writing to it. But that doesn't seem possible to do. Hence, I lose capability granularity. But it seems that sysfs doesn't allow me to do that. [Nor does a configuration system via netlink. hmm]

Do I lose? Or put from my kernel developer perspective: should we even be enabling such a use?

johannes
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux