]> git.baikalelectronics.ru Git - kernel.git/commit
KEYS: Only apply KEY_FLAG_KEEP to a key if a parent keyring has it set
authorDavid Howells <dhowells@redhat.com>
Wed, 27 Jan 2016 01:02:03 +0000 (01:02 +0000)
committerJames Morris <james.l.morris@oracle.com>
Wed, 27 Jan 2016 23:48:40 +0000 (10:48 +1100)
commitd04f707444af1ff045d7f6c093ff0664241ae491
tree9175a14f9b0ee8423aa3f9b51cac21bf444dbeda
parent886c2ed797a6a785df2cf91560b8db1387458efe
KEYS: Only apply KEY_FLAG_KEEP to a key if a parent keyring has it set

KEY_FLAG_KEEP should only be applied to a key if the keyring it is being
linked into has KEY_FLAG_KEEP set.

To this end, partially revert the following patch:

commit 22488a01cf728aeea3d47959f2299c7762a333af
Author: Mimi Zohar <zohar@linux.vnet.ibm.com>
Date:   Thu Jan 7 07:46:36 2016 -0500
KEYS: refcount bug fix

to undo the change that made it unconditional (Mimi got it right the first
time).

Without undoing this change, it becomes impossible to delete, revoke or
invalidate keys added to keyrings through __key_instantiate_and_link()
where the keyring has itself been linked to.  To test this, run the
following command sequence:

    keyctl newring foo @s
    keyctl add user a a %:foo
    keyctl unlink %user:a %:foo
    keyctl clear %:foo

With the commit mentioned above the third and fourth commands fail with
EPERM when they should succeed.

Reported-by: Stephen Gallager <sgallagh@redhat.com>
Signed-off-by: David Howells <dhowells@redhat.com>
Acked-by: Mimi Zohar <zohar@linux.vnet.ibm.com>
cc: Mimi Zohar <zohar@linux.vnet.ibm.com>
cc: keyrings@vger.kernel.org
cc: stable@vger.kernel.org
Signed-off-by: James Morris <james.l.morris@oracle.com>
security/keys/key.c