linux-kernel - Re: where is the capset kernel module?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0802061225240.23855@fbirervta.pbzchgretzou.qr>
Date:	Wed, 6 Feb 2008 12:40:20 +0100 (CET)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Jeff Chua <jeff.chua.linux@...il.com>
cc:	lkml <linux-kernel@...r.kernel.org>
Subject: Re: where is the capset kernel module?

On Feb 6 2008 18:43, Jeff Chua wrote:
>On Feb 6, 2008 4:13 PM, Jeff Chua <jeff.chua.linux@...il.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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/