where is the capset kernel module?

where is the capset kernel module?

[Jeff Chua]

Latest linux git complained about this ...

named: capset failed: Operation not permitted: please ensure that the
capset kernel module is loaded.  see insmod(8)

Where is the capset kernel module?

Thanks,
Jeff.

Re: where is the capset kernel module?

[Jeff Chua]

On Feb 6, 2008 4:13 PM, Jeff Chua <jeff.chua.linux@gmail.com> wrote:
> Latest linux git complained about this ...
>
> named: capset failed: Operation not permitted: please ensure that the
> capset kernel module is loaded.  see insmod(8)

How this started was that with the latest git linux, I got this warning ...

warning: `named' uses 32-bit capabilities (legacy support in use)

So, I recompile named and ended up with the "capset failed" problem. I
tried compiling linux with LSM, but that didn't help.

Adding "--disable-linux-caps" to named compile solved the problem.

Thanks,
Jeff.

Re: where is the capset kernel module?

[Jan Engelhardt]

On Feb 6 2008 18:43, Jeff Chua wrote:
>On Feb 6, 2008 4:13 PM, Jeff Chua <jeff.chua.linux@gmail.com> wrote:
>> Latest linux git complained about this ...
>>
>> named: capset failed: Operation not permitted: please ensure that the
>> capset kernel module is loaded.  see insmod(8)
>
>How this started was that with the latest git linux, I got this warning ...
>
>warning: `named' uses 32-bit capabilities (legacy support in use)

Yes it is a really interesting case I have seen before,
but did not bother to investigate.
Is

CONFIG_SECURITY=y
CONFIG_SECURITY_CAPABILITIES=m or y

working?

Re: where is the capset kernel module?

[Jeff Chua]

On Feb 6, 2008 7:40 PM, Jan Engelhardt <jengelh@computergmbh.de> wrote:

> >warning: `named' uses 32-bit capabilities (legacy support in use)
> Yes it is a really interesting case I have seen before,
> but did not bother to investigate.
> CONFIG_SECURITY=y
> CONFIG_SECURITY_CAPABILITIES=m or y

Tried, but didn't help.

Menuconfig can't select these as modules. So may be that's they need
to be make modular.

     [*] Enable different security models
     [*]   Socket and Networking Security Hooks (NEW)
     [*]   Default Linux Capabilities (NEW)
     [*] File POSIX Capabilities (EXPERIMENTAL)
     [ ] Root Plug Support (NEW)


Thanks,
Jeff.

Re: where is the capset kernel module?

[serge]

Quoting Jeff Chua (jeff.chua.linux@gmail.com):
> On Feb 6, 2008 7:40 PM, Jan Engelhardt <jengelh@computergmbh.de> wrote:
> 
> > >warning: `named' uses 32-bit capabilities (legacy support in use)
> > Yes it is a really interesting case I have seen before,
> > but did not bother to investigate.
> > CONFIG_SECURITY=y
> > CONFIG_SECURITY_CAPABILITIES=m or y
> 
> Tried, but didn't help.
> 
> Menuconfig can't select these as modules. So may be that's they need
> to be make modular.
> 
>      [*] Enable different security models
>      [*]   Socket and Networking Security Hooks (NEW)
>      [*]   Default Linux Capabilities (NEW)
>      [*] File POSIX Capabilities (EXPERIMENTAL)
>      [ ] Root Plug Support (NEW)

Odd, I thought the help text was originally far more helpful, including
a url.  The message isn't telling you you need a kernel module, but that
you are using an old libcap.  It isn't a real problem right now if
you're not using the SMACK LSM, but to get rid of the message upgrade
your libcap from
http://www.kernel.org/pub/linux/libs/security/linux-privs/kernel-2.6/libcap-2.05.tar.gz

thanks,
-serge

Re: where is the capset kernel module?

[Jeff Chua]

On Feb 7, 2008 11:23 AM,  <serge@hallyn.com> wrote:

> Odd, I thought the help text was originally far more helpful, including
> a url.  The message isn't telling you you need a kernel module, but that
> you are using an old libcap.  It isn't a real problem right now if
> you're not using the SMACK LSM, but to get rid of the message upgrade
> your libcap from
> http://www.kernel.org/pub/linux/libs/security/linux-privs/kernel-2.6/libcap-2.05.tar.gz

That's very useful. I'll try it this weekend.

Thanks for your help!

Jeff.

Re: where is the capset kernel module?

[Jan Engelhardt]

On Feb 6 2008 19:56, Jeff Chua wrote:
>> >warning: `named' uses 32-bit capabilities (legacy support in use)
>> Yes it is a really interesting case I have seen before,
>> but did not bother to investigate.
>> CONFIG_SECURITY=y
>> CONFIG_SECURITY_CAPABILITIES=m or y
>
>Tried, but didn't help.
>
>Menuconfig can't select these as modules. So may be that's they need
>to be make modular.

O the joy of the make-it-nonmodular patch in 2.6.24.

>     [*] Enable different security models
>     [*]   Socket and Networking Security Hooks (NEW)
>     [*]   Default Linux Capabilities (NEW)
>     [*] File POSIX Capabilities (EXPERIMENTAL)
>     [ ] Root Plug Support (NEW)