All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roy Badami <roy.badami@roboreus.com>
To: Dominick Grift <domg472@gmail.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: CentOS 5 RBAC
Date: Wed, 31 Aug 2011 19:14:42 +0100	[thread overview]
Message-ID: <4E5E7A12.9080009@roboreus.com> (raw)
In-Reply-To: <20110831174805.GC11607@localhost.localdomain>

On 31/08/2011 18:48, Dominick Grift wrote:
> On Wed, Aug 31, 2011 at 06:01:15PM +0100, Roy Badami wrote:
>> I'm trying to understand the RBAC features in the version of the mls
>> (and also strict) policies that ship with CentOS 5.6 - I'm not sure
>> if this is the best place to ask or if there's a more appropriate
>> list.
> refpolicy@oss.tresys.com is more appropriate.

Thanks - I'll bear that one in mind.
>
> When you build mls policy you get a seperate secadm role when you build strict policy then sysadm role also has the capabilities that secadm role in mls has.

Yes, so looks like it does makes sense for me to use the mls policy in 
that case.  Unfortunately in the mls policy on el5 it appears that both 
sysadm_r and secadm_r can both administer security.  secadm_r is 
preveneted from performing other systems administration, but 
unfortunately sysadm_r is not prevented from changint the selinux 
policy, etc.  This wasn't how I was hoping it would work :-(

>
> well whether the modules are installed (semodule -l | grep secadm) that i guess would be defined manually in the modules.conf for strict. if the secadm module is installed then it could be that the role is just not mapped to staff_u unless policy is mls ( see above: users file snippet)
Ah, I'd been trying to figure out how to verify what modules really were 
present in the loaded binary policy - that's very useful, thanks!  As as 
your other pointers to bits of the policy.

Regards

roy

--
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:[~2011-08-31 18:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-31 17:01 CentOS 5 RBAC Roy Badami
2011-08-31 17:15 ` Stephen Smalley
2011-08-31 18:03   ` Roy Badami
2011-08-31 18:23     ` Stephen Smalley
2011-08-31 18:25       ` Stephen Smalley
2011-09-02 11:37       ` Roy Badami
2011-09-02 12:30         ` Christopher J. PeBenito
2011-09-02 13:49           ` Roy Badami
2011-09-02 14:18             ` Dominick Grift
2011-08-31 17:24 ` Stephen Smalley
2011-08-31 18:03   ` Roy Badami
2011-08-31 17:48 ` Dominick Grift
2011-08-31 18:14   ` Roy Badami [this message]
2011-08-31 18:24     ` Dominick Grift

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=4E5E7A12.9080009@roboreus.com \
    --to=roy.badami@roboreus.com \
    --cc=domg472@gmail.com \
    --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.