From: Daniel J Walsh <dwalsh@redhat.com>
To: Stephen Smalley <sds@tycho.nsa.gov>,
"Paddie O'Brien" <paddieobrien@gmail.com>,
Selinux@tycho.nsa.gov
Subject: Re: Question on unconfined_t
Date: Mon, 17 Nov 2014 15:37:03 -0500 [thread overview]
Message-ID: <546A5C6F.6030805@redhat.com> (raw)
In-Reply-To: <546A1634.1070900@tycho.nsa.gov>
On 11/17/2014 10:37 AM, Stephen Smalley wrote:
> On 11/17/2014 09:44 AM, Paddie O'Brien wrote:
>> Hi,
>>
>> As a learning exercise I created a simple policy to sandbox a simple
>> program in its own domain.
>>
>> I had to add rules to the policy to allow the program to be executed
>> from unconfined_t. Is this normal? My understanding was that a process
>> in unconfined_t was subject only to DAC so why did I have to add this
>> rule? What does unconfined_t actually mean?
> SELinux has no intrinsic concept of unconfined_t; unconfined_t is just a
> type that is allowed to do most things by policy.
>
> _______________________________________________
> 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.
>
>
You probably did not define the type as a file_type(mytype_t)
unconfined_t is only allowed to execute file types, if you just define a
type and put it on a file, SELinux does not know if it is a port_type or
a process type (domain)
So it is not allowed.
next prev parent reply other threads:[~2014-11-17 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 14:44 Question on unconfined_t Paddie O'Brien
2014-11-17 15:37 ` Stephen Smalley
2014-11-17 20:37 ` Daniel J Walsh [this message]
2014-11-17 21:18 ` Paddie O'Brien
2014-11-17 21:54 ` Dominick Grift
2014-11-17 22:42 ` 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=546A5C6F.6030805@redhat.com \
--to=dwalsh@redhat.com \
--cc=Selinux@tycho.nsa.gov \
--cc=paddieobrien@gmail.com \
--cc=sds@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.