From: "Stephen C. Tweedie" <sct@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Stephen Smalley <sds@epoch.ncsc.mil>,
Linus Torvalds <torvalds@transmeta.com>,
"Ted Ts'o" <tytso@mit.edu>,
Andreas Gruenbacher <a.gruenbacher@computer.org>,
lkml <linux-kernel@vger.kernel.org>,
lsm <linux-security-module@wirex.com>
Subject: Re: [PATCH] Extended Attributes for Security Modules against 2.5.68
Date: 28 Apr 2003 16:59:16 +0100 [thread overview]
Message-ID: <1051545556.2021.50.camel@sisko.scot.redhat.com> (raw)
In-Reply-To: <20030423194254.A5295@infradead.org>
Hi,
On Wed, 2003-04-23 at 19:42, Christoph Hellwig wrote:
> On Wed, Apr 23, 2003 at 02:35:59PM -0400, Stephen Smalley wrote:
> > The idea of using separate attribute names for each security module was
> > already discussed at length when I posted the original RFC, and I've
> > already made the case that this is not desirable. Please see the
> > earlier discussion.
>
> No. It's not acceptable that the same ondisk structure has a different
> meaning depending on loaded modules. If the xattrs have a different
> meaning they _must_ have a different name.
I'm not convinced --- I don't see much value in trying to preserve MAC
semantics over load/unload of different security modules, so for sanity
the important thing is just to be able to detect whether a security
xattr "belongs" to the current module or not. That can be done with a
simple prefix in the xattr value itself. Trying to make multiple MAC
labels coexist in different xattrs seems to have little use.
--Stephen
prev parent reply other threads:[~2003-04-28 15:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 17:52 [PATCH] Extended Attributes for Security Modules against 2.5.68 Stephen Smalley
2003-04-23 18:17 ` Christoph Hellwig
2003-04-23 18:25 ` Chris Wright
2003-04-23 18:45 ` Christoph Hellwig
2003-04-23 19:17 ` Stephen Smalley
2003-04-23 19:26 ` Christoph Hellwig
2003-04-23 19:52 ` Stephen Smalley
2003-04-23 20:20 ` Christoph Hellwig
2003-04-24 12:55 ` Stephen Smalley
2003-04-24 13:03 ` Christoph Hellwig
2003-04-24 13:49 ` Stephen Smalley
2003-04-24 18:36 ` Chris Wright
2003-04-24 19:02 ` Stephen Smalley
2003-04-24 19:40 ` Andreas Dilger
2003-04-24 20:04 ` Stephen Smalley
2003-04-24 20:47 ` Chris Wright
2003-04-24 19:47 ` Chris Wright
2003-04-24 20:07 ` Stephen Smalley
2003-04-23 20:07 ` richard offer
2003-04-23 18:54 ` Andreas Dilger
2003-04-23 19:14 ` Stephen Smalley
2003-04-23 19:15 ` Chris Wright
2003-04-23 19:28 ` Valdis.Kletnieks
2003-04-23 19:40 ` Chris Wright
2003-04-23 19:49 ` Valdis.Kletnieks
2003-04-23 18:35 ` Stephen Smalley
2003-04-23 18:42 ` Christoph Hellwig
2003-04-23 18:59 ` Stephen Smalley
2003-04-23 19:09 ` Christoph Hellwig
2003-04-24 5:02 ` Jakob Oestergaard
2003-04-28 15:59 ` Stephen C. Tweedie [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=1051545556.2021.50.camel@sisko.scot.redhat.com \
--to=sct@redhat.com \
--cc=a.gruenbacher@computer.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@wirex.com \
--cc=sds@epoch.ncsc.mil \
--cc=torvalds@transmeta.com \
--cc=tytso@mit.edu \
/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;
as well as URLs for NNTP newsgroup(s).