From: David Howells <dhowells@redhat.com>
To: keyrings@vger.kernel.org
Cc: dhowells@redhat.com, linux-security-module@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] keys: ACLs
Date: Thu, 23 May 2019 16:58:20 +0100 [thread overview]
Message-ID: <155862710003.24863.11807972177275927370.stgit@warthog.procyon.org.uk> (raw)
Here are some patches to change the permissions model used by keys and
keyrings to be based on an ACL:
(1) Replace the permissions mask internally with an ACL that contains a
list of ACEs, each with a specific subject with a permissions mask.
Potted default ACLs are available for new keys and keyrings.
ACE subjects can be macroised to indicate the UID and GID specified on
the key (which remain). Future commits will be able to add additional
subject types, such as specific UIDs or domain tags/namespaces.
Also split a number of permissions to give finer control. Examples
include splitting the revocation permit from the change-attributes
permit, thereby allowing someone to be granted permission to revoke a
key without allowing them to change the owner; also the ability to
join a keyring is split from the ability to link to it, thereby
stopping a process accessing a keyring by joining it and thus
acquiring use of possessor permits.
(2) Provide a keyctl to allow the granting or denial of one or more
permits to a specific subject. Direct access to the ACL is not
granted, and the ACL cannot be viewed.
The patches can be found on the following branch:
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=keys-acl
David
---
David Howells (2):
KEYS: Replace uid/gid/perm permissions checking with an ACL
KEYS: Provide KEYCTL_GRANT_PERMISSION
certs/blacklist.c | 7
certs/system_keyring.c | 12 -
drivers/md/dm-crypt.c | 2
drivers/nvdimm/security.c | 2
fs/afs/security.c | 2
fs/cifs/cifs_spnego.c | 25 +
fs/cifs/cifsacl.c | 28 +-
fs/cifs/connect.c | 4
fs/crypto/keyinfo.c | 2
fs/ecryptfs/ecryptfs_kernel.h | 2
fs/ecryptfs/keystore.c | 2
fs/fscache/object-list.c | 2
fs/nfs/nfs4idmap.c | 30 +-
fs/ubifs/auth.c | 2
include/linux/key.h | 121 ++++---
include/uapi/linux/keyctl.h | 64 ++++
lib/digsig.c | 2
net/ceph/ceph_common.c | 2
net/dns_resolver/dns_key.c | 12 +
net/dns_resolver/dns_query.c | 15 +
net/rxrpc/key.c | 16 +
security/integrity/digsig.c | 31 +-
security/integrity/digsig_asymmetric.c | 2
security/integrity/evm/evm_crypto.c | 2
security/integrity/ima/ima_mok.c | 13 +
security/integrity/integrity.h | 4
.../integrity/platform_certs/platform_keyring.c | 13 +
security/keys/compat.c | 2
security/keys/encrypted-keys/encrypted.c | 2
security/keys/encrypted-keys/masterkey_trusted.c | 2
security/keys/gc.c | 2
security/keys/internal.h | 16 +
security/keys/key.c | 29 +-
security/keys/keyctl.c | 97 ++++-
security/keys/keyring.c | 27 +-
security/keys/permission.c | 356 ++++++++++++++++++--
security/keys/persistent.c | 27 +-
security/keys/proc.c | 20 +
security/keys/process_keys.c | 86 ++++-
security/keys/request_key.c | 34 +-
security/keys/request_key_auth.c | 15 +
security/selinux/hooks.c | 16 +
security/smack/smack_lsm.c | 3
43 files changed, 868 insertions(+), 285 deletions(-)
next reply other threads:[~2019-05-23 15:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 15:58 David Howells [this message]
2019-05-23 15:58 ` [PATCH 1/2] KEYS: Replace uid/gid/perm permissions checking with an ACL David Howells
2019-07-10 1:15 ` Eric Biggers
2019-07-10 1:35 ` Eric Biggers
2019-07-30 3:49 ` Eric Biggers
2019-07-31 1:16 ` Eric Biggers
2019-08-07 2:58 ` Eric Biggers
2019-08-14 22:41 ` Eric Biggers
2019-05-23 15:58 ` [PATCH 2/2] KEYS: Provide KEYCTL_GRANT_PERMISSION David Howells
2019-07-09 20:42 ` Eric Biggers
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=155862710003.24863.11807972177275927370.stgit@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).