From: David Howells <dhowells@redhat.com>
To: torvalds@linux-foundation.org
Cc: dhowells@redhat.com, jmorris@namei.org, keyrings@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] Keys: Set 1 - Miscellany for 5.3
Date: Fri, 05 Jul 2019 22:03:39 +0100 [thread overview]
Message-ID: <26702.1562360619@warthog.procyon.org.uk> (raw)
Hi Linus,
Here's my first block of keyrings changes for the next merge window. I've
divided up the set into four blocks, but they need to be applied in order
as they would otherwise conflict with each other.
These are some miscellaneous keyrings fixes and improvements:
(1) Fix a bunch of warnings from sparse, including missing RCU bits and
kdoc-function argument mismatches
(2) Implement a keyctl to allow a key to be moved from one keyring to
another, with the option of prohibiting key replacement in the
destination keyring.
(3) Grant Link permission to possessors of request_key_auth tokens so that
upcall servicing daemons can more easily arrange things such that only
the necessary auth key is passed to the actual service program, and
not all the auth keys a daemon might possesss.
(4) Improvement in lookup_user_key().
(5) Implement a keyctl to allow keyrings subsystem capabilities to be
queried.
The keyutils next branch has commits to make available, document and test
the move-key and capabilities code:
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/keyutils.git/log
They're currently on the 'next' branch.
David
---
The following changes since commit a188339ca5a396acc588e5851ed7e19f66b0ebd9:
Linux 5.2-rc1 (2019-05-19 15:47:09 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/keys-misc-20190619
for you to fetch changes up to 45e0f30c30bb131663fbe1752974d6f2e39611e2:
keys: Add capability-checking keyctl function (2019-06-19 13:27:45 +0100)
----------------------------------------------------------------
Keyrings miscellany
----------------------------------------------------------------
David Howells (9):
keys: sparse: Fix key_fs[ug]id_changed()
keys: sparse: Fix incorrect RCU accesses
keys: sparse: Fix kdoc mismatches
keys: Change keyring_serialise_link_sem to a mutex
keys: Break bits out of key_unlink()
keys: Hoist locking out of __key_link_begin()
keys: Add a keyctl to move a key between keyrings
keys: Grant Link permission to possessers of request_key auth keys
keys: Add capability-checking keyctl function
Eric Biggers (1):
keys: Reuse keyring_index_key::desc_len in lookup_user_key()
Documentation/security/keys/core.rst | 21 +++
include/linux/key.h | 13 +-
include/uapi/linux/keyctl.h | 17 +++
kernel/cred.c | 4 +-
security/keys/compat.c | 6 +
security/keys/internal.h | 7 +
security/keys/key.c | 27 +++-
security/keys/keyctl.c | 90 +++++++++++-
security/keys/keyring.c | 278 ++++++++++++++++++++++++++++-------
security/keys/process_keys.c | 26 ++--
security/keys/request_key.c | 9 +-
security/keys/request_key_auth.c | 4 +-
12 files changed, 418 insertions(+), 84 deletions(-)
next reply other threads:[~2019-07-05 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 21:03 David Howells [this message]
2019-07-09 3:15 ` pr-tracker-bot
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=26702.1562360619@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®