public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@osdl.org>
To: James Morris <jmorris@redhat.com>
Cc: Kurt Garloff <garloff@suse.de>,
	Linux kernel list <linux-kernel@vger.kernel.org>,
	Chris Wright <chrisw@osdl.org>,
	Stephen Smalley <sds@epoch.ncsc.mil>
Subject: Re: [PATCH] [LSM] Rework LSM hooks
Date: Tue, 10 Aug 2004 13:23:11 -0700	[thread overview]
Message-ID: <20040810132311.R1924@build.pdx.osdl.net> (raw)
In-Reply-To: <Xine.LNX.4.44.0408100922490.7461-100000@dhcp83-76.boston.redhat.com>; from jmorris@redhat.com on Tue, Aug 10, 2004 at 09:29:58AM -0400

* James Morris (jmorris@redhat.com) wrote:
> On Tue, 10 Aug 2004, Kurt Garloff wrote:
> > The first patch patch does just change the selinux default; so you
> > need to enable with selinux=1.
> 
> This issue has been through a couple of iterations and the current scheme
> where if you have SELinux enabled, it is on by default, is aimed at being
> more secure by default.  On some platforms, boot parameters are not
> feasible.  To allow SELinux to be disable for these, the /selinux/disable
> node was implemented, which allows SELinux to be unregistered during boot.  
> I suggest you investigate using this; look at what Fedora does.

Could make selinux_enabled value configurable.  I don't really like the
extra configuration, but if it's more vendor neutral to have config
not only control if you can have bootparam, but also default value,
then perhaps it'd be useful.

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

  reply	other threads:[~2004-08-10 20:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10  8:57 [PATCH] [LSM] Rework LSM hooks Kurt Garloff
2004-08-10 13:29 ` James Morris
2004-08-10 20:23   ` Chris Wright [this message]
2004-08-10 20:27     ` James Morris
2004-08-10 20:43       ` Chris Wright
2004-08-11  1:55         ` James Morris
2004-08-10 14:16 ` James Morris
2004-08-10 15:02   ` Alan Cox
2004-08-10 19:22     ` James Morris
2004-08-10 20:00       ` Chris Wright
2004-08-10 20:07         ` James Morris
2004-08-10 20:12           ` Chris Wright
2004-08-10 20:31             ` James Morris
2004-08-11  8:47               ` David Mosberger
2004-08-11 15:25                 ` Chris Wright
2004-08-11 18:12                   ` David Mosberger
2004-08-11 18:16                     ` Chris Wright
2004-08-11 22:22             ` Kurt Garloff
2004-08-12  1:23               ` James Morris
2004-08-12  3:58                 ` Greg KH
2004-08-12 18:15                   ` Chris Wright
2004-08-12 18:17                 ` Chris Wright
2004-08-16 14:19               ` Takashi Iwai
2004-08-11 22:19   ` Kurt Garloff
2004-08-12  1:20     ` James Morris
2004-08-12  2:03       ` Kurt Garloff

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=20040810132311.R1924@build.pdx.osdl.net \
    --to=chrisw@osdl.org \
    --cc=garloff@suse.de \
    --cc=jmorris@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sds@epoch.ncsc.mil \
    /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