From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@epoch.ncsc.mil>, SE Linux <selinux@tycho.nsa.gov>
Subject: I am attempting to add a secadm_r
Date: Thu, 07 Apr 2005 11:38:21 -0400 [thread overview]
Message-ID: <425553ED.1040703@redhat.com> (raw)
I do not want to get in a conversation about how many ways there are
around this, from sysadm_r. I know that, but when I was at DOD
a couple of weeks ago they stated that they wanted a separate role from
policy management, from the role of the system administrator. They
did not care about this being protected, but wanted a way to stop
accidentally modifying the machine. In DOD the System Administrator and
the Security Administrator are different roles.
Any ways trying a simple experiment I have added the following roles
role secadm_r types sysadm_t
role secadm_r types checkpolicy_t
role secadm_r types newrole_t
And I add secadm_r as a "root" role in the users file.
Now when I try to newrole from root:sysadm_r:sysadm_t to
root:secadm_r:sysadm_t
I get a process transition failure
from
root:sysadm_r:newrole_t to root:secadm_r:sysadm_t.
What am I missing?
the
allow newrole_t sysadm_t:process transition;
rule exists
--
--
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 reply other threads:[~2005-04-07 15:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 15:38 Daniel J Walsh [this message]
2005-04-07 16:46 ` I am attempting to add a secadm_r Luke Kenneth Casson Leighton
2005-04-07 17:00 ` Stephen Smalley
2005-04-07 17:45 ` Luke Kenneth Casson Leighton
2005-04-07 17:39 ` Stephen Smalley
2005-04-07 18:33 ` Luke Kenneth Casson Leighton
2005-04-19 4:43 ` Russell Coker
2005-04-07 16:54 ` Stephen Smalley
2005-04-07 16:55 ` Stephen Smalley
2005-04-07 17:10 ` Stephen Smalley
2005-04-07 19:25 ` Daniel J Walsh
2005-04-07 19:37 ` Stephen Smalley
2005-04-19 4:32 ` Russell Coker
-- strict thread matches above, loose matches on Subject: below --
2005-04-08 0:50 Chad Hanson
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=425553ED.1040703@redhat.com \
--to=dwalsh@redhat.com \
--cc=sds@epoch.ncsc.mil \
--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.