lkml.org 
[lkml]   [2019]   [Feb]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Subject[RFC PATCH 0/9] keys: Namespacing
From
Date

Here are some development patches to make keys and keyrings namespace aware by
the following means:

(1) Firstly some miscellaneous patches to make it simpler:

(a) Invalidate rather than revoke request_key() authentication keys to
recycle them more quickly.

(b) Remove request_key_async*() as they aren't used and would have to be
namespaced.

(c) Simplify key index_key handling so that the word-sized chunks
assoc_array requires don't have to be shifted about, making it easier
to add more bits into the key.

(d) Cache the hash value so that we don't have to calculate on every key
we examine during a search (it involves a bunch of multiplications).

[Note: Some of these want to be split out and sent separately]

(2) Make it possible to include the target namespace in which the key shall
operate in the index_key. This will allow the possibility of multiple
keys with the same description, but different target domains to be held
in the same keyring.

(3) Make it so that keys are effectively invalidated by removal of a domain
tag, causing them to be garbage collected.

(4) Institute a network namespace domain tag that allows keys to be
differentiated by the network namespace in which they operate. New keys
that are of a type marked 'KEY_TYPE_NET_DOMAIN' are assigned the network
domain in force when they are created.

(5) Make it so that the desired network namespace can be handed down into the
request_key() mechanism. This allows AFS, NFS, etc. to request keys
specific to the network namespace of the superblock.

This also means that the keys in the DNS record cache are thenceforth
namespaced, provided network filesystems pass the appropriate network
namespace down into dns_query().

For DNS, AFS and NFS are good; CIFS and Ceph are not. Other cache
keyrings, such as idmapper keyrings, also need to set the domain tag.

(6) Make it so that keyring names are per-user-namespace so that they're not
accessible cross-user-namespace.


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-namespace

David
---
David Howells (9):
keys: Invalidate used request_key authentication keys
keys: Kill off request_key_async{,_with_auxdata}
keys: Simplify key description management
keys: Cache the hash value to avoid lots of recalculation
keys: Include target namespace in match criteria
keys: Garbage collect keys for which the domain has been removed
keys: Network namespace domain tag
keys: Pass the network namespace into request_key mechanism
KEYS: Namespace keyring names


fs/afs/addr_list.c | 4 -
fs/afs/dynroot.c | 7 +
fs/cifs/dns_resolve.c | 3
fs/nfs/dns_resolve.c | 2
include/linux/dns_resolver.h | 3
include/linux/key-type.h | 3
include/linux/key.h | 46 ++++++-
include/linux/user_namespace.h | 5 +
include/net/net_namespace.h | 4 +
kernel/user.c | 3
kernel/user_namespace.c | 7 +
net/ceph/messenger.c | 3
net/core/net_namespace.c | 18 +++
net/dns_resolver/dns_key.c | 1
net/dns_resolver/dns_query.c | 6 +
net/rxrpc/key.c | 6 +
security/keys/gc.c | 2
security/keys/internal.h | 6 +
security/keys/key.c | 9 +
security/keys/keyctl.c | 2
security/keys/keyring.c | 248 ++++++++++++++++++++++------------------
security/keys/persistent.c | 2
security/keys/request_key.c | 90 +++++++--------
23 files changed, 288 insertions(+), 192 deletions(-)

\
 
 \ /
  Last update: 2019-02-14 17:57    [W:0.615 / U:0.024 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site