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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080207032331.GA25762@vino.hallyn.com>
Date:	Wed, 6 Feb 2008 21:23:31 -0600
From:	serge@...lyn.com
To:	Jeff Chua <jeff.chua.linux@...il.com>
Cc:	Jan Engelhardt <jengelh@...putergmbh.de>,
	lkml <linux-kernel@...r.kernel.org>,
	Andrew Morgan <morgan@...nel.org>
Subject: Re: where is the capset kernel module?

Quoting Jeff Chua (jeff.chua.linux@...il.com):
> On Feb 6, 2008 7:40 PM, Jan Engelhardt <jengelh@...putergmbh.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
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ