Re: [PATCH v1.3 4/4] keys: add new key-type encrypted

[Mimi Zohar <zohar@linux.vnet.ibm.com>]

On Tue, 2010-11-16 at 17:50 +0000, David Howells wrote:
> Mimi Zohar <zohar@linux.vnet.ibm.com> wrote:
> 
> > I actually like keyctl requiring 'trusted:' or 'user:'.  Forcing the
> > user to indicate which type of key they want, is actually good - no
> > misunderstandings.
> 
> You still need to prefix the description of a user-defined key so that you
> don't collide with other people who're also using user-defined keys for random things.

ok

> > Another benefit, would be allowing 'keyctl update' to update the key
> > description, not the key type.
> 
> You mean you want to change the description on a key?
> 
> David

No, this just updates the name of the key used to encrypt/decrypt the
encrypted key. For example, the encrypted key evm-key is initially
encrypted/decrypted using 'kmk-trusted'.  After the update, it is
encrypted/decrypted with 'kmk'.  Both now are trusted keys.

$ keyctl show
Session Keyring
       -3 --alswrv    500   500  keyring: _ses
117908125 --alswrv    500    -1   \_ keyring: _uid.500
501967942 --alswrv    500   500       \_ trusted: kmk-trusted
317523177 --alswrv    500   500       \_ encrypted: evm-key
666437381 --alswrv    500   500       \_ trusted: kmk
$ keyctl print 317523177
trusted:kmk-trusted 32 ca0ebb83594f14781460 ...

$ keyctl update 317523177 "update trusted:kmk"
$ keyctl print 317523177
trusted:kmk 32 ca0ebb83594f1478146 ....

Mimi