[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46CFA6F2.9030209@kernel.org>
Date: Fri, 24 Aug 2007 20:50:10 -0700
From: Andrew Morgan <morgan@...nel.org>
To: "Serge E. Hallyn" <serge@...lyn.com>, Adrian Bunk <bunk@...nel.org>
CC: chrisw@...s-sol.org, linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org
Subject: Re: [2.6 patch] remove securebits
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
FWIW, in the mm kernel, I've actually already removed them when one
configures without capabilities.
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.23-rc3/2.6.23-rc3-mm1/broken-out/v3-file-capabilities-alter-behavior-of-cap_setpcap.patch
Other than writing a custom module, so far as I can tell, there is/was
no way to set them anyway.
I'd obviously prefer to wait for the mm-merge process to complete and
minimize the churn in this area, but I basically agree that the bits as
implemented are pretty useless in their current form. In a per-process
mode (with filesystem capability support) they are much more useful...
Cheers
Andrew
Serge E. Hallyn wrote:
> Quoting Adrian Bunk (bunk@...nel.org):
>> It seems that since it was added in kernel 2.2.0 (sic) securebits
>> was never used.
>>
>> This patch therefore removes it.
>
> Actually IIUC Andrew Morgan had plans of making securebits per-process,
> which would make them far more usable.
>
> Now maybe he'd just as soon start with a clean slate... Andrew?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFGz6bwQheEq9QabfIRAjx5AKCZSFZ0dv4HTUtUYtm6OdVlOUi3ewCdGHzE
TnoeF19cOljfiyntgkcSCbE=
=lW84
-----END PGP SIGNATURE-----
-
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