Message	SHA1
KEYS: Make the system 'trusted' keyring viewable by userspace ... Give the root user the ability to read the system keyring and put read permission on the trusted keys added during boot. The latter is actually more theoretical than real for the moment as asymmetric keys do not currently provide a read operation. Signed-off-by: Mimi Zohar <zohar@us.ibm.com> Signed-off-by: David Howells <dhowells@redhat.com> Mimi Zohar   authored and   David Howells   commited 2013-09-25 17:17:01 +01:00	af34cb0c3d
KEYS: Add a 'trusted' flag and a 'trusted only' flag ... Add KEY_FLAG_TRUSTED to indicate that a key either comes from a trusted source or had a cryptographic signature chain that led back to a trusted key the kernel already possessed. Add KEY_FLAGS_TRUSTED_ONLY to indicate that a keyring will only accept links to keys marked with KEY_FLAGS_TRUSTED. Signed-off-by: David Howells <dhowells@redhat.com> Reviewed-by: Kees Cook <keescook@chromium.org> David Howells   commited 2013-09-25 17:17:01 +01:00	008643b86c
KEYS: Separate the kernel signature checking keyring from module signing ... Separate the kernel signature checking keyring from module signing so that it can be used by code other than the module-signing code. Signed-off-by: David Howells <dhowells@redhat.com> David Howells   commited 2013-09-25 17:17:01 +01:00	b56e5a17b6