RE: [pkcs11] CKA_PUBLIC_KEY_INFO

["Burns, Robert" <Robert.Burns@thalesesec.com>]

Michael,

Based on this proposal, it appears that now every token that wants to work with public keys will be required to have DER encoding/decoding functions for all public keys.  In the (somewhat distant) past, specific care was given to support tokens which only needed to work with the objects themselves by ensuring that the standard did not force tokens to implement DER/BER encoding rules (many reasons for this).  Is there a way in which we could support having this field default to "empty" so that tokens are not forced to DER encode their public keys if they don't want to?  That way, tokens can support the field, or choose not to.

Thanks,

Bob



> -----Original Message-----
> From: pkcs11@lists.oasis-open.org [mailto:pkcs11@lists.oasis-open.org] On
> Behalf Of Michael StJohns
> Sent: Tuesday, April 09, 2013 7:35 PM
> To: pkcs11@lists.oasis-open.org
> Subject: [pkcs11] CKA_PUBLIC_KEY_INFO
> 
> Attached is an edit of the appropriate sections of PKCS11 v2.30 to add
> support for CKA_PUBLIC_KEY_INFO.
> 
> Additions are highlighted.  Assuming this is acceptable, I'll provide the
> appropriate edits for the public key sections to describe the encoding of the
> public key info field in SubjectPublicKeyInfo
> 
> Mike