From: dE <de.techno@gmail.com>
To: selinux@tycho.nsa.gov
Subject: Re: Significance of SELinux user and roles on objects.
Date: Fri, 23 May 2014 10:31:53 +0530 [thread overview]
Message-ID: <537ED641.6010100@gmail.com> (raw)
In-Reply-To: <1400743958.10370.0.camel@x220.localdomain>
On 05/22/14 13:02, Dominick Grift wrote:
> On Thu, 2014-05-22 at 12:25 +0530, dE wrote:
>> On 05/20/14 19:12, Christopher J. PeBenito wrote:
>>> The kernel will create files with object_r regardless
>> Is this defined in the policy or is hard coded in the kernel?
> Hard coded into the kernel
>
>> 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.
>
Ok. Thanks for clarifying all this.
next prev parent reply other threads:[~2014-05-23 5:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 5:01 Significance of SELinux user and roles on objects dE
2014-05-20 13:42 ` Christopher J. PeBenito
2014-05-22 6:55 ` dE
2014-05-22 7:32 ` Dominick Grift
2014-05-23 5:01 ` dE [this message]
2014-05-23 13:42 ` Stephen Smalley
2014-05-23 15:45 ` dE
2014-05-23 15:55 ` Stephen Smalley
2014-05-24 3:39 ` dE
2014-05-27 12:36 ` Christopher J. PeBenito
2014-05-27 12:51 ` Stephen Smalley
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=537ED641.6010100@gmail.com \
--to=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.