From: Stephen Smalley <sds@tycho.nsa.gov>
To: Richard Haines <richard_c_haines@btinternet.com>,
selinux@vger.kernel.org
Cc: dhowells@redhat.com
Subject: Re: [RFC PATCH] libsepol: Add 'key_perms' policy capability
Date: Mon, 3 Feb 2020 10:36:02 -0500 [thread overview]
Message-ID: <f9406d34-8509-97cc-6879-37f4547a49d2@tycho.nsa.gov> (raw)
In-Reply-To: <20200202193632.15205-1-richard_c_haines@btinternet.com>
On 2/2/20 2:36 PM, Richard Haines wrote:
> Allow the new key class permissions 'inval, revoke, join and clear' to be
> handled.
>
> Signed-off-by: Richard Haines <richard_c_haines@btinternet.com>
Since the 'genfs_seclabel_symlinks' policy capability has already been
queued for merge [1][2], I think this one will have to be bumped to the
next policy capability bit after it.
[1]
https://lore.kernel.org/selinux/20200124184221.322248-1-cgzones@googlemail.com/
[2]
https://lore.kernel.org/selinux/20200131183900.3507-1-cgzones@googlemail.com/
> ---
> libsepol/include/sepol/policydb/polcaps.h | 1 +
> libsepol/src/polcaps.c | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/libsepol/include/sepol/policydb/polcaps.h b/libsepol/include/sepol/policydb/polcaps.h
> index dc9356a6..de0c67b6 100644
> --- a/libsepol/include/sepol/policydb/polcaps.h
> +++ b/libsepol/include/sepol/policydb/polcaps.h
> @@ -13,6 +13,7 @@ enum {
> POLICYDB_CAPABILITY_ALWAYSNETWORK,
> POLICYDB_CAPABILITY_CGROUPSECLABEL,
> POLICYDB_CAPABILITY_NNP_NOSUID_TRANSITION,
> + POLICYDB_CAPABILITY_KEYPERMS,
> __POLICYDB_CAPABILITY_MAX
> };
> #define POLICYDB_CAPABILITY_MAX (__POLICYDB_CAPABILITY_MAX - 1)
> diff --git a/libsepol/src/polcaps.c b/libsepol/src/polcaps.c
> index b9dc3526..48213c54 100644
> --- a/libsepol/src/polcaps.c
> +++ b/libsepol/src/polcaps.c
> @@ -12,6 +12,7 @@ static const char *polcap_names[] = {
> "always_check_network", /* POLICYDB_CAPABILITY_ALWAYSNETWORK */
> "cgroup_seclabel", /* POLICYDB_CAPABILITY_SECLABEL */
> "nnp_nosuid_transition", /* POLICYDB_CAPABILITY_NNP_NOSUID_TRANSITION */
> + "key_perms", /* POLICYDB_CAPABILITY_KEYPERMS */
> NULL
> };
>
>
prev parent reply other threads:[~2020-02-03 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 19:36 [RFC PATCH] libsepol: Add 'key_perms' policy capability Richard Haines
2020-02-03 15:36 ` Stephen Smalley [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=f9406d34-8509-97cc-6879-37f4547a49d2@tycho.nsa.gov \
--to=sds@tycho.nsa.gov \
--cc=dhowells@redhat.com \
--cc=richard_c_haines@btinternet.com \
--cc=selinux@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).