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: Wed, 15 Nov 2017 18:48:51 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1711151847390.19987@localhost> (raw)
In-Reply-To: <1510582716.30953.2.camel@tycho.nsa.gov>
On Mon, 13 Nov 2017, Stephen Smalley wrote:
> Was also wondering if the name read for the init namespace ought to
> just be the empty string instead of the magic "init" value to make it
> consistent with the fact that there is no xattr suffix.
Makes sense. It could also be "security.selinux", and always exactly
match the xattr name.
--
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
WARNING: multiple messages have this Message-ID (diff)
From: James Morris <james.l.morris@oracle.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: linux-security-module@vger.kernel.org, selinux@tycho.nsa.gov
Subject: Re: [RFC v0.1][PATCH] selinuxns: extend namespace support to security.selinux xattrs
Date: Wed, 15 Nov 2017 18:48:51 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1711151847390.19987@localhost> (raw)
In-Reply-To: <1510582716.30953.2.camel@tycho.nsa.gov>
On Mon, 13 Nov 2017, Stephen Smalley wrote:
> Was also wondering if the name read for the init namespace ought to
> just be the empty string instead of the magic "init" value to make it
> consistent with the fact that there is no xattr suffix.
Makes sense. It could also be "security.selinux", and always exactly
match the xattr name.
--
James Morris
<james.l.morris@oracle.com>
next prev parent reply other threads:[~2017-11-15 7:48 UTC|newest]
Thread overview: 22+ 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 10:04 ` James Morris
2017-10-30 15:55 ` Casey Schaufler
2017-10-30 15:55 ` Casey Schaufler
2017-10-30 19:16 ` Stephen Smalley
2017-10-30 19:16 ` Stephen Smalley
2017-10-31 3:11 ` James Morris
2017-10-31 3:11 ` James Morris
2017-10-31 13:00 ` Stephen Smalley
2017-10-31 13:00 ` Stephen Smalley
2017-10-31 14:04 ` Stephen Smalley
2017-10-31 14:04 ` Stephen Smalley
2017-11-01 6:40 ` James Morris
2017-11-01 6:40 ` James Morris
2017-11-01 15:22 ` Stephen Smalley
2017-11-01 15:22 ` Stephen Smalley
2017-11-13 6:45 ` James Morris
2017-11-13 6:45 ` James Morris
2017-11-13 14:18 ` Stephen Smalley
2017-11-13 14:18 ` Stephen Smalley
2017-11-15 7:48 ` James Morris [this message]
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.1711151847390.19987@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 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.