public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Andrew G. Morgan" <morgan@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: dhowells@redhat.com, serue@us.ibm.com,
	linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org
Subject: [PATCH 0/4]: security: filesystem capabilities (was Re: [PATCH] capabilities: refactor kernel code + bugfix)
Date: Thu, 26 Jun 2008 01:46:35 -0700	[thread overview]
Message-ID: <4863576B.7020408@kernel.org> (raw)
In-Reply-To: <20080625163035.b409d693.akpm@linux-foundation.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Andrew,

Configuring filesystem capabilities is still tagged experimental, and
the effect of the "security fix" part of this change is conditional on
filesystem capabilities being configured. This late in the rc cycle, I'm
not convinced that the risk of this bugfix isn't greater than the benefit.

If you disagree, there is another "security" problem with filesystem
capabilities and strace, and I've been exploring the fix. This is also
the last fix I think we need before we can remove the experimental
attribute on filesystem capabilities.

As such, I'll follow this up with four patches. The first two are
bugfixes (affecting kernels configured with filesystem support); the
third is the refactoring; and the fourth removes the experimental tag on
filesystem capability support.

Cheers

Andrew

Andrew Morton wrote:
| On Fri, 20 Jun 2008 08:38:19 -0700
| "Andrew G. Morgan" <morgan@kernel.org> wrote:
|
|> From 8a2bffcb5363295ea43ef42c84c121a8e8c7ffa0 Mon Sep 17 00:00:00 2001
|> From: Andrew G. Morgan <morgan@kernel.org>
|> Date: Fri, 20 Jun 2008 08:16:06 -0700
|> Subject: [PATCH] Refactor filesystem capability support in main kernel.
|>
[...]
| This is one helluva large (security!) patch for so late in -rc.
|
| Could we please split out the bugfix for 2.6.26 (is it needed in 2.6.25
| too?) and hold the refactoring back for 2.6.27?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFIY1dr+bHCR3gb8jsRAsUDAJsGSGgj7TVq29CoTIOff3p1xkHYYwCfWFQ9
Qm4ZQthlkNikLDoMuhalBx4=
=8NT4
-----END PGP SIGNATURE-----

      reply	other threads:[~2008-06-26  8:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-20 15:38 [PATCH] capabilities: refactor kernel code + bugfix Andrew G. Morgan
2008-06-23 15:23 ` Serge E. Hallyn
2008-06-25 23:30 ` Andrew Morton
2008-06-26  8:46   ` Andrew G. Morgan [this message]

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=4863576B.7020408@kernel.org \
    --to=morgan@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=serue@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox