[Dnsmasq-discuss] setting capabilities failed with CONFIG_SECURITY=n

[Simon Kelley]

On 04/01/11 20:04, Ryan Nowakowski wrote:

> On x86, I don't have to:
>
> root at OpenWrt:~# uname -a
> Linux OpenWrt 2.6.32.10 #10 Tue Jan 4 13:42:56 CST 2011 i686 GNU/Linux
> root at OpenWrt:~# ps -aef | grep dns
>   1255 nobody     640 S    /usr/sbin/dnsmasq -K -D -y -Z -b -E -s lan -S /lan/ -
>   5834 root       932 S    grep dns
> root at OpenWrt:~# cat /proc/config.gz | gunzip | grep SECURITY
> # CONFIG_SECURITY is not set
> # CONFIG_SECURITYFS is not set
> # CONFIG_SECURITY_FILE_CAPABILITIES is not set
> root at OpenWrt:~#
>
> Any idea why?
>

The dnsmasq FAQ says:

Q: Dnsmasq fails to start up with a message about capabilities.
    Why did that happen and what can do to fix it?

A: Change your kernel configuration: either deselect CONFIG_SECURITY
    _or_ select CONFIG_SECURITY_CAPABILITIES. Alternatively, you can
    remove the need to set capabilities by running dnsmasq as root.


but that may well be out of date, since CONFIG_SECURITY_CAPABILITIES is 
apparently not there any more.

Simon.