From: Dominick Grift <domg472@gmail.com>
To: selinux@tycho.nsa.gov
Subject: Re: CentOS 5 RBAC
Date: Fri, 2 Sep 2011 16:18:07 +0200 [thread overview]
Message-ID: <20110902141806.GA25154@localhost.localdomain> (raw)
In-Reply-To: <4E60DEE6.4030605@roboreus.com>
[-- Attachment #1: Type: text/plain, Size: 1597 bytes --]
On Fri, Sep 02, 2011 at 02:49:26PM +0100, Roy Badami wrote:
>
> >>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().
> >
>
> Ah, thank you! I would never have found that on my own, given the
> number of macros and attributes that everything indirects through!
>
> So I'm beginning to realise that sysadm_r is probably the wrong
> starting point for me. I think what I really want to be doing is
> probably creating a new 'limited admin' role (perhaps based on
> staff_r) and adding in only those permissions the role actually
> needs.
You could create a new role based off of the userdom_base_user_template, and then map this newly created role to the staff_u user. So that staff_u can newrole to the "new role". Then just tailor the role to your requirements.
A key property of the "base_user_template" is that this is not a login user template. So the role can only be access through newrole/su. The new role cannot interact with user home directories.
>
> Thanks again,
>
> roy
>
> --
> Roy Badami
> Roboreus Ltd
> 1 New Oxford Street
> London WC1A 1NU
>
>
> --
> 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.
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-09-02 14:18 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 [this message]
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=20110902141806.GA25154@localhost.localdomain \
--to=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.