From: james.l.morris@oracle.com (James Morris)
To: linux-security-module@vger.kernel.org
Subject: [RFC v0.1][PATCH] selinuxns: extend namespace support to security.selinux xattrs
Date: Mon, 13 Nov 2017 17:45:24 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1711131734230.32474@localhost> (raw)
In-Reply-To: <1509458646.20694.10.camel@tycho.nsa.gov>
On Tue, 31 Oct 2017, Stephen Smalley wrote:
> This btw would be a bit cleaner if we dropped the .ns. portion of the
> name, such that we would have:
> security.selinux # xattr name in the init namespace
> security.selinux.vmN # xattr name in the vmN namespace
> security.selinux.vmN.vmM # xattr name in the vmN.vmM namespace
Ok, just to clarify, the namespace name in the last example is "vmN.vmM",
not "vmM" ?
i.e. the namespaces are always hierarchical, and the security labels are
identified by that hierarchy. If you enter vmM from the init namespace,
for example, the security labels for it are distinct from the labels under
vmN. On disk, you would have both:
security.selinux.vmM
security.selinux.vmN.vmM
which are independent.
Each of these instances would potentially inherit different labels, and
have different provenance characteristics, so this seems necessary in any
case.
--
James Morris
<james.l.morris@oracle.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-11-13 6:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 10:04 [RFC v0.1][PATCH] selinuxns: extend namespace support to security.selinux xattrs James Morris
2017-10-30 15:55 ` Casey Schaufler
2017-10-30 19:16 ` Stephen Smalley
2017-10-31 3:11 ` James Morris
2017-10-31 13:00 ` Stephen Smalley
2017-10-31 14:04 ` Stephen Smalley
2017-11-01 6:40 ` James Morris
2017-11-01 15:22 ` Stephen Smalley
2017-11-13 6:45 ` James Morris [this message]
2017-11-13 14:18 ` Stephen Smalley
2017-11-15 7:48 ` James Morris
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=alpine.LFD.2.20.1711131734230.32474@localhost \
--to=james.l.morris@oracle.com \
--cc=linux-security-module@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).