All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: russell@coker.com.au
Cc: "Christopher J. PeBenito" <cpebenito@tresys.com>,
	James Morris <jmorris@namei.org>,
	SELinux List <selinux@tycho.nsa.gov>
Subject: Re: MCS policy patch
Date: Tue, 07 Feb 2006 08:34:00 -0500	[thread overview]
Message-ID: <43E8A1C8.9020407@redhat.com> (raw)
In-Reply-To: <200602072259.16871.russell@coker.com.au>

Russell Coker wrote:
> My previous message was unclear.
>
> On Tuesday 07 February 2006 14:19, Russell Coker <russell@coker.com.au> wrote:
>   
>>> We can't have these hardcoded types.  What we need is similar to how the
>>> mls constraints are handled.  Attributes and interfaces need to be added
>>> to the mls module, then the above domains would use the interfaces to
>>> gain these attributes.
>>>       
>> Actually I never planned to have it like that.  But the lack of support for
>> range transition statements outside the base module prevents me from doing
>> what I want.
>>     
>
> What I want to do is to have the init scripts run at SystemHigh and have a 
> range transition for every daemon that doesn't need such access (most 
> daemons), doing this without range_transition in all modules would be a gross 
> hack.  Also I am considering having some daemons such as Postfix run with 
> some processes at SystemHigh and some at s0.
>
> Another thing, I think that a default user login should not have SystemHigh, 
> maybe s0:c0.c127.  The reason is that the administrator will add accounts, 
> have a running system with files labelled on disk and in backup storage, and 
> THEN they will decide that they want one particular account to have more 
> access than the default.  This will be a major PITA if every account already 
> has all the categories.  If we make the default level be s0:c0.c127 then that 
> still gives plenty of levels to choose from (it shouldn't restrict real use 
> of the system) and it allows adding new users with more access than the 
> default.
>
> This one only just occurred to me, but it's something that I think is quite 
> important to be in FC5T3 to avoid the current situation propagating too far.
>
>   
Default users login with s0.  They have no categories.  This information 
is gathered  via the seusers interface.
If the admin wants to give a user access to categories he will need to 
use semanage to give this access.

By default all processes should run at s0, currently we have no way to 
change this level that a daemon will run at.
Correct?

--
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:[~2006-02-07 13:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-03 14:18 MCS policy patch Russell Coker
2006-02-03 19:31 ` James Morris
2006-02-03 23:10   ` Russell Coker
2006-02-04  0:15 ` Daniel J Walsh
2006-02-06 23:04 ` Christopher J. PeBenito
2006-02-07  3:19   ` Russell Coker
2006-02-07 11:59     ` Russell Coker
2006-02-07 13:34       ` Daniel J Walsh [this message]

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=43E8A1C8.9020407@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=cpebenito@tresys.com \
    --cc=jmorris@namei.org \
    --cc=russell@coker.com.au \
    --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.