From: Casey Schaufler <casey@schaufler-ca.com>
To: Michael C Thompson <thompsmc@us.ibm.com>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: [RFC] clarifications for -l to newrole.1
Date: Fri, 12 Jan 2007 09:22:34 -0800 (PST) [thread overview]
Message-ID: <587927.74563.qm@web36613.mail.mud.yahoo.com> (raw)
In-Reply-To: <45A7B31D.6000001@us.ibm.com>
--- Michael C Thompson <thompsmc@us.ibm.com> wrote:
> Currently, in the MLS policy, the default behaviour
> is to have users
> login at SystemLow. If this is not what you would
> expect, then we should
> probably change the default levels assumed for users
> on login.
Allowing users to log in at SystemLow would not
be consistant with current best practice. I know
that neither Trusted Solaris nor Trusted Irix
allows that, and I don't think that HP/UX does
either. Even allowing for the additional
protections provided by TE letting users run with
the same MLS value as system files (unless you
have something lower than low!) is going to
set off warning bells in certain circles. Why
have MLS if you aren't going to use it to
protect your system data, after all? And yes,
I understand that there's lots more to SELinux
policy enforcement than MLS, and that the other
protections are more than sufficient to protect
the system files from users. Even with that,
users should be segregated from the system using
MLS since MLS is available. Belts, bracers,
garters, elastic and velcro make for a happy
and swift evaluation and an end user that
understands how the system is protected.
Casey Schaufler
casey@schaufler-ca.com
--
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:[~2007-01-12 17:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 20:39 [RFC] clarifications for -l to newrole.1 Michael C Thompson
2007-01-11 21:02 ` Stephen Smalley
2007-01-11 21:24 ` Stephen Smalley
2007-01-11 22:07 ` Russell Coker
2007-01-12 14:36 ` Stephen Smalley
2007-01-12 16:11 ` Michael C Thompson
2007-01-12 17:22 ` Casey Schaufler [this message]
2007-01-12 18:07 ` Joe Nall
2007-01-12 19:48 ` Casey Schaufler
2007-01-12 17:57 ` Stephen Smalley
2007-01-13 6:26 ` Russell Coker
2007-01-11 23:34 ` Michael C Thompson
2007-01-12 0:04 ` Michael C Thompson
2007-01-12 15:16 ` Stephen Smalley
2007-01-12 16:19 ` Michael C Thompson
2007-01-12 21:52 ` Stephen Smalley
2007-01-14 20:02 ` Michael C Thompson
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=587927.74563.qm@web36613.mail.mud.yahoo.com \
--to=casey@schaufler-ca.com \
--cc=selinux@tycho.nsa.gov \
--cc=thompsmc@us.ibm.com \
/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.