On Tue, 2010-11-16 at 14:08 +0000, David Howells wrote: > Mimi Zohar <zohar@xxxxxxxxxxxxxxxxxx> wrote: > > > Am assuming you mean something like this: > > > > keyctl add encrypted name "new trusted:master-key-name keylen" ring > > keyctl add encrypted name "new user:master-key-name keylen" ring > > > > and, as you said, works without changing the API. > > No, that's not what I mean. I maeant that when your internal functions look > for the user key, they should preface the description with a prefix. > > It should be handled in request_user_key() or request_master_key(). The > description given to request_trusted_key() should have the prefix applied > there. There's no need to mention it at all in the encrypted key add_key > command line. > > David I actually like keyctl requiring 'trusted:' or 'user:'. Forcing the user to indicate which type of key they want, is actually good - no misunderstandings. Another benefit, would be allowing 'keyctl update' to update the key description, not the key type. Mimi -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
