LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: James Morris <jmorris@namei.org>
Cc: Alexey Dobriyan <adobriyan@sw.ru>,
	linux-kernel@vger.kernel.org, eparis@parisplace.org,
	casey@schaufler-ca.com
Subject: Re: SMACK or SELinux, but not both
Date: Tue, 26 Feb 2008 07:39:36 -0500	[thread overview]
Message-ID: <1204029576.2804.260.camel@moss-spartans.epoch.ncsc.mil> (raw)
In-Reply-To: <Xine.LNX.4.64.0802262020001.527@us.intercode.com.au>


On Tue, 2008-02-26 at 20:28 +1100, James Morris wrote:
> On Tue, 26 Feb 2008, Alexey Dobriyan wrote:
> 
> > If SELinux is registered before SMACK, SMACK panics after
> > register_security() call.
> > 
> > If SMACK is registered before SELinux, SELinux panics after
> > register_security() call.
> > 
> > Consequently allmodconfig kernel doesn't boot. It would be nice if
> > some Kconfig magic to exclude each other will be in place.
> 
> People want to be able to select the security model at boot time, so the 
> option to build both LSMs is required.
> 
> You can stop SELinux from attempting to register as an LSM via selinux=0, 
> which should allow you to boot with just Smack enabled.

Ideally, one could just boot with security=<module> to select the
desired primary security module.  security=smack, security=selinux, or
security=capability.

Having to specify selinux=0 smack=0 foo=0 just to get bar wouldn't be
pretty.  Not that anyone would want to do that, of course...

-- 
Stephen Smalley
National Security Agency


  reply	other threads:[~2008-02-26 12:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-26  9:09 Alexey Dobriyan
2008-02-26  9:28 ` James Morris
2008-02-26 12:39   ` Stephen Smalley [this message]
2008-02-28 21:11     ` Bill Davidsen

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=1204029576.2804.260.camel@moss-spartans.epoch.ncsc.mil \
    --to=sds@tycho.nsa.gov \
    --cc=adobriyan@sw.ru \
    --cc=casey@schaufler-ca.com \
    --cc=eparis@parisplace.org \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: SMACK or SELinux, but not both' \
    /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

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).