All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morgan <morgan@kernel.org>
To: "Serge E. Hallyn" <serge@hallyn.com>, Adrian Bunk <bunk@kernel.org>
Cc: chrisw@sous-sol.org, linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org
Subject: Re: [2.6 patch] remove securebits
Date: Fri, 24 Aug 2007 20:50:10 -0700	[thread overview]
Message-ID: <46CFA6F2.9030209@kernel.org> (raw)
In-Reply-To: <20070824211942.GA24478@vino.hallyn.com>

-----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@kernel.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-----

  reply	other threads:[~2007-08-25  3:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-24 21:06 [2.6 patch] remove securebits Adrian Bunk
2007-08-24 21:19 ` Serge E. Hallyn
2007-08-25  3:50   ` Andrew Morgan [this message]
2007-08-25 18:28     ` Adrian Bunk
2007-08-27 15:09       ` Serge E. Hallyn
2007-08-27 15:17         ` Adrian Bunk
2007-08-27 15:28           ` Serge E. Hallyn
2007-08-27 15:58             ` Adrian Bunk
2007-08-28  7:20               ` Andrew Morgan
2007-08-28 14:38                 ` Serge E. Hallyn
2007-08-28 18:19                 ` Serge E. Hallyn
2007-08-30  0:51                   ` Andrew Morgan
2007-08-30 13:26                     ` Serge E. Hallyn

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=46CFA6F2.9030209@kernel.org \
    --to=morgan@kernel.org \
    --cc=bunk@kernel.org \
    --cc=chrisw@sous-sol.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=serge@hallyn.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.