mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chris@wirex.com>
To: richard offer <offer@sgi.com>
Cc: Stephen Smalley <sds@epoch.ncsc.mil>,
	Linus Torvalds <torvalds@transmeta.com>,
	"Ted Ts'o" <tytso@mit.edu>, Stephen Tweedie <sct@redhat.com>,
	lkml <linux-kernel@vger.kernel.org>,
	Andreas Gruenbacher <ag@bestbits.at>,
	lsm <linux-security-module@wirex.com>
Subject: Re: [RFC][PATCH] Extended Attributes for Security Modules
Date: Thu, 17 Apr 2003 18:07:45 -0700	[thread overview]
Message-ID: <20030417180745.J29431@figure1.int.wirex.com> (raw)
In-Reply-To: <1020130000.1050612787@changeling.engr.sgi.com>; from offer@sgi.com on Thu, Apr 17, 2003 at 01:53:07PM -0700

* richard offer (offer@sgi.com) wrote:
> * frm chris@wirex.com "04/17/03 13:30:59 -0700" | sed '1,$s/^/* /'
> * 
> * This is the core issue.  Personally, I'd rather stick to simple strings
> * and per-module attributes rooted at a common point.  This is simplest
> * for userspace tools.  But the attribute namespace is effectively flat,
> * so it's a question of simplicity for locating the attributes.  A simple
> * getxattr(2) vs. a listxattr(2) plus multiple getxattr(2).  Unfortunately,
> * this points at a single standard name I think...
> 
> Good point. Okay you've conviced me enough that while I don't agree more
> than 51%, I'm at least going to shut up until the next time.

Heh, it's a valid question.  I like per-module attributes, but I don't
think they are as nice for userland tools.  I don't acutally like
encoding namesapce into the attribute value, but I'm not sure the
alternative is much different/better.

> Would it make sense to have a single "backup/restore security label" tool
> that is distributed alongside LSM rather than relying on each module writer
> developing their own.

You mean to ensure that labels are accumulated rather than replaced?
Could be useful I suppose.

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

  reply	other threads:[~2003-04-18  1:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-10 12:06 Stephen Smalley
2003-04-13 22:57 ` Andreas Gruenbacher
2003-04-15 13:41   ` Stephen Smalley
2003-04-15 16:58     ` richard offer
2003-04-15 18:19       ` Stephen Smalley
2003-04-16 13:47       ` Stephen Smalley
2003-04-16 22:02         ` richard offer
2003-04-17  4:24           ` Stephen Smalley
2003-04-17 20:30             ` Chris Wright
2003-04-17 20:53               ` richard offer
2003-04-18  1:07                 ` Chris Wright [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-15 18:33 Chuck Ebbert
2003-04-15 18:56 ` Chris Wright
2003-04-08 20:26 Stephen Smalley

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=20030417180745.J29431@figure1.int.wirex.com \
    --to=chris@wirex.com \
    --cc=ag@bestbits.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@wirex.com \
    --cc=offer@sgi.com \
    --cc=sct@redhat.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

all inboxes | Powered by JetHome®