From: Daniel J Walsh <dwalsh@redhat.com>
To: dE <de.techno@gmail.com>, selinux@tycho.nsa.gov
Subject: Re: Listing restrictions on roles.
Date: Thu, 03 Jul 2014 05:39:01 -0400 [thread overview]
Message-ID: <53B524B5.3000109@redhat.com> (raw)
In-Reply-To: <53B39378.1090003@gmail.com>
On 07/02/2014 01:07 AM, dE wrote:
> There seem to exist additional non-transition restrictions on roles
> which define when will a process be able to execute as a certain role.
>
> For e.g. a process which runs from a login shell cannot have system_r
> role. How do I list such rules?
>
> Looking at role transition rules, a transition to system_r should be
> allowed --
>
> sesearch --role_allow | grep system_r\;
> ...
> allow unconfined_r system_r;
> ...
>
> And the sudo process runs as unconfined_r --
>
> ps auxZ | grep sudo
> system_u:unconfined_r:unconfined_t:s0 root 669 0.0 0.4 206860 3356
> pts/1 S+ 10:28 0:00 sudo -r unconfined_r nano
>
> But sudo -r system_r nano fails.
> _______________________________________________
> Selinux mailing list
> Selinux@tycho.nsa.gov
> To unsubscribe, send email to Selinux-leave@tycho.nsa.gov.
> To get help, send an email containing "help" to
> Selinux-request@tycho.nsa.gov.
The type has to be available to the role. In the case of sudo -r
system_r nano, if the type to be run is unconfined_t, then SELinux would
end up with a label like
sytem_u:system_r:unconfined_t:s0
But I don't believe unconfined_t can run in the system_r role.
seinfo -rsystem_r -x | grep unconfined_t
To make your sudo command run, you would also need to select the type.
sudo -r sysadm_r -t nano_t nano ...
Or something like that where nano_t is available to the system_r role.
next prev parent reply other threads:[~2014-07-03 9:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 5:07 Listing restrictions on roles dE
2014-07-03 9:39 ` Daniel J Walsh [this message]
2014-07-05 16:41 ` dE
2014-07-07 15:23 ` Daniel J Walsh
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=53B524B5.3000109@redhat.com \
--to=dwalsh@redhat.com \
--cc=de.techno@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.