[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1211294742.7486.137.camel@moss-spartans.epoch.ncsc.mil>
Date: Tue, 20 May 2008 10:45:42 -0400
From: Stephen Smalley <sds@...ho.nsa.gov>
To: Amit Shah <shahamit@...il.com>
Cc: "Serge E. Hallyn" <serue@...ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>,
netdev@...r.kernel.org, bugme-daemon@...zilla.kernel.org,
Andrew Morgan <morgan@...nel.org>
Subject: Re: [Bugme-new] [Bug 10748] New: dhclient fails to run;
capabilities error
On Tue, 2008-05-20 at 19:37 +0530, Amit Shah wrote:
> On Tue, May 20, 2008 at 7:28 PM, Stephen Smalley <sds@...ho.nsa.gov> wrote:
> >
> > On Tue, 2008-05-20 at 09:38 -0400, Stephen Smalley wrote:
> >> Which means that he is using the dummy security module.
> >> And it appears that a prior commit moved KEEPCAPS handling from
> >> core prctl() to cap_task_prctl(), but didn't replicate it in
> >> the dummy_task_prctl().
> >>
> >> The dummy module really needs to die.
> >
> > Question for the bug reporter: did you really mean to build a kernel
> > without capabilities support? Surprise! They don't really work when
> > disabled.
>
> No; I was just trying out some random configs. This config worked till
> .25 properly though.
The dummy module is generally in the untenable position of having to lie
to userspace or break the existing capability-related system call
interface. It should just go away, and make capability the default
module (w/ stubs for the rest of the LSM hooks as with dummy). Then
CONFIG_SECURITY=n will yield the same result as CONFIG_SECURITY=y w/o
any further options.
--
Stephen Smalley
National Security Agency
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists