All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Gruenbacher <agruen@suse.de>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-security-module@vger.kernel.org,
	James Morris <jmorris@redhat.com>,
	Andrew Morgan <morgan@kernel.org>, Andrew Morton <akpm@osdl.org>,
	Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH 1/2] file capabilities: add no_file_caps switch (v2)
Date: Tue, 23 Sep 2008 00:08:30 +0200	[thread overview]
Message-ID: <200809230008.31025.agruen@suse.de> (raw)
In-Reply-To: <20080922215032.GB502@us.ibm.com>

On Monday, 22 September 2008 23:50:32 Serge E. Hallyn wrote:
> Quoting Andreas Gruenbacher (agruen@suse.de):
> > I agree. These other behaviorial changes should not depend on
> > CONFIG_SECURITY_FILE_CAPABILITIES; the old behavior should just be fixed
> > instead.
>
> That of course would be the point of the patch 3/3, which removes
> CONFIG_SECURITY_FILE_CAPABILITIES as a config option.  Should I
> do that

I think yes.

> when I redo the patch as per Stephen's suggestion to use filecaps=0/1?

This will require to adjust our installer, which uses no_file_caps already. I 
don't think that filecaps=0/1 is really necessary, but it I can life with 
either.

Thanks,
Andreas

  reply	other threads:[~2008-09-22 22:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-22 18:48 [PATCH 1/2] file capabilities: add no_file_caps switch (v2) Serge E. Hallyn
2008-09-22 18:49 ` [PATCH 2/2] file capabilities: turn on by default Serge E. Hallyn
2008-09-22 19:03   ` Randy Dunlap
2008-09-22 19:56     ` Serge E. Hallyn
2008-09-22 21:09       ` Randy Dunlap
2008-09-22 22:53       ` Chris Wright
2008-09-22 19:16 ` [PATCH 1/2] file capabilities: add no_file_caps switch (v2) Stephen Smalley
2008-09-22 20:09   ` Andreas Gruenbacher
2008-09-22 21:50     ` Serge E. Hallyn
2008-09-22 22:08       ` Andreas Gruenbacher [this message]
2008-09-23  6:48       ` James Morris
2008-09-22 22:57 ` Chris Wright
2008-09-23 15:51   ` Serge E. Hallyn
     [not found] <beYE7-1Xc-41@gated-at.bofh.it>
     [not found] ` <beZ72-2GM-5@gated-at.bofh.it>
     [not found]   ` <bf035-3Tp-5@gated-at.bofh.it>
2008-09-23  7:21     ` Markku Savela
  -- strict thread matches above, loose matches on Subject: below --
2008-08-28 19:54 Serge Hallyn
2008-08-29  0:35 ` Andrew G. Morgan

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=200809230008.31025.agruen@suse.de \
    --to=agruen@suse.de \
    --cc=akpm@osdl.org \
    --cc=chrisw@sous-sol.org \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=morgan@kernel.org \
    --cc=sds@tycho.nsa.gov \
    --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 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.