All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karl MacMillan <kmacmill@redhat.com>
To: casey@schaufler-ca.com
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
	Crispin Cowan <crispin@novell.com>,
	selinux@tycho.nsa.gov, linux-security-module@vger.kernel.org
Subject: Re: Current/Future Plans to Support Stacking LSM Modules
Date: Thu, 18 Jan 2007 11:53:09 -0500	[thread overview]
Message-ID: <45AFA5F5.2080908@redhat.com> (raw)
In-Reply-To: <14268.46782.qm@web36613.mail.mud.yahoo.com>

Casey Schaufler wrote:
> --- Stephen Smalley <sds@tycho.nsa.gov> wrote:
> 
> 
>> To the contrary, the LSPP work significantly
>> leverages the work already
>> done to integrate SELinux and makes use of the
>> SELinux interfaces for
>> applications.  It also leverages SELinux TE to
>> address aspects such as
>> MLS overrides.  By doing it within the context of
>> SELinux, it gained the
>> benefit of a unified security model and interface. 
>> Which one doesn't get from LSM.
> 
> There are others who would argue that SELinux
> has abandoned the Linux privilege model and
> thus disrupted the unity of the existing
> security model.
> 

No clue what this means.

> I don't understand why the SELinux crew seems
> so intent on making it difficult to implement
> alternatives. Last year it was "let's ditch LSM".
> Now it's "Everyone hates stacking". Give it a
> rest already.
> 

1) Stacking is possible now, just not arbitrary stacking by an admin.

2) Not having arbitrary stacking in no way limits alternatives. It just 
forces the use of a single alternative at a time or explicit development 
to make alternatives work together.

3) The objections, if you read them, are about whether the correctness 
of arbitrarily stacked modules can be reasonably expected or verified. 
It is not an effort to limit alternatives.

There are real disagreements here, but please stop overstating the 
differences and misconstruing (willfully?) peoples positions.

Karl




--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2007-01-18 16:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-16 18:08 Current/Future Plans to Support Stacking LSM Modules Tom Fortmann
2007-01-16 18:27 ` Stephen Smalley
2007-01-16 18:46 ` Casey Schaufler
     [not found]   ` <45AF5539.2020608@novell.com>
2007-01-18 12:50     ` Stephen Smalley
     [not found]       ` <45AF7643.3080200@novell.com>
2007-01-18 13:53         ` Stephen Smalley
2007-01-18 16:36           ` Casey Schaufler
2007-01-18 16:53             ` Karl MacMillan [this message]
2007-01-18 18:12               ` Casey Schaufler
2007-01-18 18:50                 ` Serge E. Hallyn
2007-01-18 19:30                   ` Casey Schaufler
2007-01-18 20:29                 ` Stephen Smalley
2007-01-18 21:32                   ` Casey Schaufler
2007-01-23 23:24                     ` Russell Coker
2007-01-24 16:09                       ` Paul Moore
2007-01-18 17:28           ` 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=45AFA5F5.2080908@redhat.com \
    --to=kmacmill@redhat.com \
    --cc=casey@schaufler-ca.com \
    --cc=crispin@novell.com \
    --cc=linux-security-module@vger.kernel.org \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    /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.