[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [pkcs11] Groups - EdDSA Using Additional Key Types uploaded uploaded
Hi Dieter, Thanks for the comments. Sorry for not providing any feedback sooner. Here are some quick responses. We can discuss them more on the call or offline. U1: I agree and thanks for the updates. U2: I would prefer not to add a new choice as that would further confuse and complicate things. My preference would be to either adopt an existing OID, or possibly
define our own under OASIS. The problem now is that there are many OIDs for these curves and algorithms defined by many different entities (gnupg, pkix, cryptlib…etc) in very inconsistent ways. Some of them are documented as being specific for the curve
parameters, while others are more specific to the curve+algorithm combination. I would prefer to try and align with at least one of them, however it really is a mess out there. Whether we select existing one, or define our own, I think we would still need to document that many OIDs exist and vendors will most likely support more than
one OID. U3: I agree. Given that we are specifically referencing an RFC, it would be safe to move that detail to the PKCS#11 document. This would be good as encoding
is something that is often debated. From: Dieter Bong [mailto:Dieter.Bong@utimaco.com]
Hi Darren, Really good proposal.
I have included comments, and fixed a few typos, in the attached document. We mainly see one remaining issue w.r.t. curve naming (comment U2 in the document). Thanks, Dieter From:
pkcs11@lists.oasis-open.org [mailto:pkcs11@lists.oasis-open.org]
On Behalf Of Darren Johnson Submitter's message
This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited. E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender. Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]