Skip to content

keys: play nicely with user namespaces

Serge E. Hallyn containers 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 18 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3keys: distinguish per-uid keys in different namespaceskernel/user.c security/keys/internal.h security/keys/key.c +3 more+17 -60 replies
2/3keys: consider user namespace in key_permissionsecurity/keys/permission.c+5 -00 replies
3/3keys: skip keys from another user namespacesecurity/keys/keyring.c+3 -00 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/3] keys: play nicely with user namespaces

Hi David,

so here is a first attempt at getting keys and uid namespaces to play nice. The semantics need some discussion. As I recall Eric and yourself appeared to agree that some keyrings should be inherited into child user namespaces. I segragate them cleanly bc that appears to be the simplest thing to do especially given the use of i.e. lookup_by_name("uid.500"). IMO it shouldn't be a big problem - userspace can always list keys it wants into a file, start a new user namespace, then re-read them out of the tempfile...

Comments appreciated.

thanks,
-serge