All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael C Thompson <thompsmc@us.ibm.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: russell@coker.com.au, SE Linux <selinux@tycho.nsa.gov>,
	Klaus Weidner <klaus@atsec.com>,
	Daniel J Walsh <dwalsh@redhat.com>
Subject: Re: [RFC] clarifications for -l to newrole.1
Date: Fri, 12 Jan 2007 10:11:09 -0600	[thread overview]
Message-ID: <45A7B31D.6000001@us.ibm.com> (raw)
In-Reply-To: <1168612577.7993.477.camel@moss-spartans.epoch.ncsc.mil>

Stephen Smalley wrote:
> On Fri, 2007-01-12 at 09:07 +1100, Russell Coker wrote:
>> On Friday 12 January 2007 08:02, Stephen Smalley <sds@tycho.nsa.gov> wrote:
>>>> EXAMPLE
>>>>         Changing sensitivity only:
>>>>            # id -Z
>>>>            user:role:type:SystemLow-SystemHigh
>>>>            # newrole -l Unclassified
>>>>            # id -Z
>>>>            user:role:type:Unclassified-SystemHigh
>>> How does SystemLow differ from Unclassified here (in meaning, not just
>>> value)?  If SystemLow is supposed to be a special label for system
>>> objects, then why have users login at that level at all?
>> In the context of the man page I don't think it matters.  The purpose is to
>> clarify an interface that confuses many people.
> 
> I'm concerned about two things:
> - the example being meaningful to the user (what does SystemLow mean
> relative to Unclassified in the user's mind),
> - the actual policy being correct (is it correct for users to login at
> SystemLow and then switch to Unclassified manually, or should they be
> logging in at Unclassified directly and not even allowed to directly
> login at SystemLow).

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.


Mike


--
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-12 16:11 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 [this message]
2007-01-12 17:22         ` Casey Schaufler
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=45A7B31D.6000001@us.ibm.com \
    --to=thompsmc@us.ibm.com \
    --cc=dwalsh@redhat.com \
    --cc=klaus@atsec.com \
    --cc=russell@coker.com.au \
    --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.