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@xxxxxxxxxxxxx with the words "unsubscribe selinux" without quotes as the message.
