From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Roy Badami <roy.badami@roboreus.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>, <selinux@tycho.nsa.gov>
Subject: Re: CentOS 5 RBAC
Date: Fri, 2 Sep 2011 08:30:56 -0400 [thread overview]
Message-ID: <4E60CC80.1030001@tresys.com> (raw)
In-Reply-To: <4E60BFF0.1070002@roboreus.com>
On 09/02/11 07:37, Roy Badami wrote:
>
>> I think that would work and avoid the need to modify/rebuild the
>> existing policy.
>>
>> However, be aware that the sysadm vs secadm distinction is largely
>> illusory even if you do this. See this thread for further discussion:
>> http://marc.info/?t=105457894700002&r=1&w=2
>>
>
> Any idea what it is that gives sysadm_t write access to selinux_config_t:file ?
>
> I can see the rule when I opne the binary policy in apol but I haven't had much luck tracking down where it comes from in the policy source.
The auth_manage_all_files_except_shadow() call in userdom_admin_user_template().
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
--
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.
next prev parent reply other threads:[~2011-09-02 12:30 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 [this message]
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
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=4E60CC80.1030001@tresys.com \
--to=cpebenito@tresys.com \
--cc=roy.badami@roboreus.com \
--cc=sds@tycho.nsa.gov \
--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.