3 May 2006 21:01
RE: Elliptic Curve Cryptography with PKIX
Russ Housley <housley <at> vigilsec.com>
2006-05-03 19:01:21 GMT
2006-05-03 19:01:21 GMT
RFC 3280 does not provide as much guidance as I would like. Section
4.1.2.7 says the following about the Subject Public Key Info field:
This field is used to carry the public key and identify the algorithm
with which the key is used (e.g., RSA, DSA, or Diffie-Hellman). The
algorithm is identified using the AlgorithmIdentifier structure
specified in section 4.1.1.2. The object identifiers for the
supported algorithms and the methods for encoding the public key
materials (public key and parameters) are specified in [PKIXALGS].
Section 4.1.1.2 includes these words:
The algorithm identifier is used to identify a cryptographic
algorithm. The OBJECT IDENTIFIER component identifies the algorithm
(such as DSA with SHA-1). The contents of the optional parameters
field will vary according to the algorithm identified.
It does not really provide much guidance to developers of AlgorithmIdentifiers.
I characterize the X9.62 approach as using the OBJECT IDENTIFIER to
name a class of elliptic curve algorithms, and then using a portion
of the parameters to list the members of that class that are
acceptable for the subject public key.
I am very interested to know how this fits with real implementations.
My suspicion is that implementation that support key agreement are
used to looking into the parameter to determine if the public key is
a member of the same group. This is needed for static-static
(Continue reading)
RSS Feed