LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: serge@hallyn.com
To: Jeff Chua <jeff.chua.linux@gmail.com>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
lkml <linux-kernel@vger.kernel.org>,
Andrew Morgan <morgan@kernel.org>
Subject: Re: where is the capset kernel module?
Date: Wed, 6 Feb 2008 21:23:31 -0600 [thread overview]
Message-ID: <20080207032331.GA25762@vino.hallyn.com> (raw)
In-Reply-To: <b6a2187b0802060356r19e59e67lfa572939545872e@mail.gmail.com>
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
next prev parent reply other threads:[~2008-02-07 3:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-06 8:13 where is the capset kernel module? Jeff Chua
2008-02-06 10:43 ` Jeff Chua
2008-02-06 11:40 ` Jan Engelhardt
2008-02-06 11:56 ` Jeff Chua
2008-02-07 3:23 ` serge [this message]
2008-02-07 10:14 ` Jeff Chua
2008-02-08 0:22 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080207032331.GA25762@vino.hallyn.com \
--to=serge@hallyn.com \
--cc=jeff.chua.linux@gmail.com \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=morgan@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).