All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul.moore@hp.com>
To: Jeremiah Jahn <jeremiah@goodinassociates.com>
Cc: selinux <selinux@tycho.nsa.gov>
Subject: Re: secadm question
Date: Fri, 15 Feb 2008 10:18:57 -0500	[thread overview]
Message-ID: <200802151018.57712.paul.moore@hp.com> (raw)
In-Reply-To: <1203088187.3669.241.camel@bluejay.goodinassociates.com>

On Friday 15 February 2008 10:09:47 am Jeremiah Jahn wrote:
> So if I change my build.conf to be mls I should be up and running.
> I'm on RHEL5 btw

Yes, setting the TYPE to "mls" should enable the secadm_r role.  If you 
don't need the latest Reference Policy, there is a MLS policy as part 
of RHEL5 - it's what was used for the recent (okay, maybe not that 
recent anymore) Common Criteria LSPP evaluations.

> On Fri, 2008-02-15 at 08:55 -0500, Paul Moore wrote:
> > On Thursday 14 February 2008 6:09:43 pm Jeremiah Jahn wrote:
> > > I see a number of places where the secadm_r role shows up, but It
> > > doesn't show up in the list of users and what not, Is there
> > > something simple I need to enable it, or 	do I need to build it
> > > from scratch? My goal it to have sysadm not able to modify policy
> > > enforcement, and my secadm not be able to do anything but. If
> > > there is a standard way to do this, I'd love to know.
> >
> > I believe the secadm_r role is only defined for the "mls" policy
> > builds; if you are running a "mcs" (the Fedora default) policy I
> > don't think the secadm_r role is present.

-- 
paul moore
linux security @ hp

--
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.

  parent reply	other threads:[~2008-02-15 15:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14 23:09 secadm question Jeremiah Jahn
2008-02-15 13:55 ` Paul Moore
2008-02-15 15:09   ` Jeremiah Jahn
2008-02-15 15:16     ` Stephen Smalley
2008-02-15 15:39       ` Christopher J. PeBenito
2008-02-15 16:09         ` Jeremiah Jahn
2008-02-15 16:09           ` Christopher J. PeBenito
2008-02-15 16:14             ` Jeremiah Jahn
2008-02-15 16:23               ` Christopher J. PeBenito
2008-02-15 16:36                 ` Jeremiah Jahn
2008-02-15 18:40                   ` Christopher J. PeBenito
2008-02-15 21:21                   ` secadm/sysadm discussion Daniel J Walsh
2008-02-15 21:22                   ` Daniel J Walsh
2008-02-17 11:17                     ` Russell Coker
2008-02-18 13:37                     ` Christopher J. PeBenito
2008-02-18 17:01                       ` Chad Hanson
2008-02-19 14:48                       ` Daniel J Walsh
2008-02-22 14:39                         ` Jeremiah Jahn
2008-02-15 15:18     ` Paul Moore [this message]
2008-02-15 15:27       ` secadm question 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=200802151018.57712.paul.moore@hp.com \
    --to=paul.moore@hp.com \
    --cc=jeremiah@goodinassociates.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.