All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: "Christopher J. PeBenito" <cpebenito@tresys.com>
Cc: SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Latest diffs in policy
Date: Tue, 16 May 2006 10:44:49 -0400	[thread overview]
Message-ID: <4469E561.9070306@redhat.com> (raw)
In-Reply-To: <1147786502.31984.22.camel@sgc>

Christopher J. PeBenito wrote:
> On Mon, 2006-05-15 at 16:54 -0400, Daniel J Walsh wrote:
>   
>> Christopher J. PeBenito wrote:
>>     
>>>> Separation of the auditadm from secadm and sysadm changes for auditd files.
>>>>     
>>>>         
>>> Filesystem association is missing.  This also brings along more problems
>>> like labeling.  There isn't much real separation between auditadm from
>>> the other admin roles, so this doesn't seem to have real benefits.
>>>   
>>>       
>> Required for LSPP.  auditadm is not allowed to do anything but manage 
>> audit subsystem.
>> secadmin can only manage selinux stuff.  sysadmin can only do everything 
>> not done by auditadm
>> and secadm.
>>     
>
> I don't see how we're accomplishing this if secadm, auditadm, and sysadm
> are using the admin_user_template().  It gives a lot of access including
> raw disk access, signalling all domains, managing the source and binary
> policies (explicitly given), and managing all files in general except
> shadow, and running insmod.  The current implementation doesn't allow
> for fine grained role definition yet (it is a planned improvement).
>
>   
Yes I am about to remove secadm and auditadm from admin_user_template to 
remove these privs.

--
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-05-16 14:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-15 15:58 Latest diffs in policy Daniel J Walsh
2006-05-15 18:56 ` Christopher J. PeBenito
2006-05-15 20:54   ` Daniel J Walsh
2006-05-15 22:15     ` Casey Schaufler
2006-05-16 13:35     ` Christopher J. PeBenito
2006-05-16 14:44       ` Daniel J Walsh [this message]
2006-05-16 15:37         ` Christopher J. PeBenito
2006-05-17 14:58 ` Christopher J. PeBenito

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=4469E561.9070306@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=cpebenito@tresys.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.