From: Paul Moore <paul@paul-moore.com>
To: Nicolas Iooss <nicolas.iooss@m4x.org>,
Stephen Smalley <sds@tycho.nsa.gov>
Cc: selinux@tycho.nsa.gov
Subject: Re: Labeling nsfs filesystem
Date: Fri, 8 Jan 2016 18:12:11 -0500 [thread overview]
Message-ID: <CAHC9VhQ6c5VrRK3m7mB=+Myexsr9RbTjfSdf+qcWx_J+9B8iUA@mail.gmail.com> (raw)
In-Reply-To: <568ED656.5030106@tycho.nsa.gov>
On Thu, Jan 7, 2016 at 4:19 PM, Stephen Smalley <sds@tycho.nsa.gov> wrote:
> On 01/07/2016 03:36 PM, Nicolas Iooss wrote:
>>
>> Hello,
>>
>> Since Linux 3.19 targets of /proc/PID/ns/* symlinks have lived in a fs
>> separated from /proc, named nsfs [1]. These targets are used to enter
>> the namespace of another process by using setns() syscall [2]. On old
>> kernels, they were labeled with procfs default type (for example
>> "getfilecon /proc/self/ns/uts" returned system_u:object_r:proc_t:s0).
>> When using a recent kernel with a policy without nsfs support, the
>> inodes are not labeled, as reported for example in Fedora bug #1234757
>> [3]. As I encounter this issue on my systems, I asked yesterday on the
>> refpolicy ML how nsfs inodes should be labeled [4].
>>
>> After digging a little bit about the possibilities, here is a summary of
>> the options I have considered so far.
>>
>> Option 1: define a new type to label nsfs inodes, nsfs_t. This works as
>> expected (c.f. [5] for more details) ...
>
> Only option 1 makes sense to me.
Agreed.
--
paul moore
www.paul-moore.com
prev parent reply other threads:[~2016-01-08 23:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 20:36 Labeling nsfs filesystem Nicolas Iooss
2016-01-07 21:19 ` Stephen Smalley
2016-01-08 13:00 ` Christopher J. PeBenito
2016-01-08 14:13 ` Stephen Smalley
2016-01-08 14:24 ` Christopher J. PeBenito
2016-01-08 23:12 ` Paul Moore [this message]
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='CAHC9VhQ6c5VrRK3m7mB=+Myexsr9RbTjfSdf+qcWx_J+9B8iUA@mail.gmail.com' \
--to=paul@paul-moore.com \
--cc=nicolas.iooss@m4x.org \
--cc=sds@tycho.nsa.gov \
--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.