From: Tom <tom@lemuria.org>
To: SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: Enable SELinux via boot parameter
Date: Wed, 3 Sep 2003 14:54:24 +0200 [thread overview]
Message-ID: <20030903145423.D3990@lemuria.org> (raw)
In-Reply-To: <1062592181.18568.321.camel@moss-spartans.epoch.ncsc.mil>; from sds@epoch.ncsc.mil on Wed, Sep 03, 2003 at 08:29:41AM -0400
On Wed, Sep 03, 2003 at 08:29:41AM -0400, Stephen Smalley wrote:
> It is already the case that you need to specify 'enforcing=1' to boot an
> enforcing kernel if you enabled development support. How many people
> disable development support?
More once SE gets more stable and production systems get deployed.
> And if you do disable development support,
> do you also keep around a second kernel that you can boot for emergency
> recovery?
Not on a production machine. I'd insist on a from-CD boot there for
recovery.
I'd love to have a way to ensure that if _this_ kernel was booted, it
_does_ use SE.
--
PGP/GPG key: http://web.lemuria.org/pubkey.html
pub 1024D/2D7A04F5 2002-05-16 Tom Vogt <tom@lemuria.org>
Key fingerprint = C731 64D1 4BCF 4C20 48A4 29B2 BF01 9FA1 2D7A 04F5
--
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.
next prev parent reply other threads:[~2003-09-03 12:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 23:46 Enable SELinux via boot parameter James Morris
2003-09-03 3:07 ` Chris PeBenito
2003-09-03 6:38 ` Brian May
2003-09-03 7:12 ` Tom
2003-09-03 12:29 ` Stephen Smalley
2003-09-03 12:54 ` Tom [this message]
2003-09-03 16:31 ` James Morris
2003-09-03 17:54 ` Tom
2003-09-03 19:27 ` Chris PeBenito
2003-09-04 4:49 ` Russell Coker
2003-09-03 15:17 ` Chris PeBenito
2003-09-03 12:24 ` 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=20030903145423.D3990@lemuria.org \
--to=tom@lemuria.org \
--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.