SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

ECC X.509 Certificate Format

bernad avatar
bernad
17 diapositives · 723 Views · May 09, 2013

ECC X.509 Certificate Format . Discussion. Goal. Enable and standardize the use of elliptic curve keys within the X.509 framework. 2. Objectives. Specify how ECC keys and their usage are indicated within X.509 certificates Simple Flexible Generic. 3. Today’s Situation.

#500s bc #507 #506 #505 #500s #504 #error-correcting code #jackanory
ECC X.509 Certificate Format - slide 1
01 / 17ECC X.509 Certificate Format
1 / 17

Télécharger la présentation

ECC X.509 Certificate Format
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. ECC X.509 Certificate Format Discussion Peter de Rooij Certicom Corp. pderooij@certicom.com (650) 312-7995

  2. Goal • Enable and standardize the use of elliptic curve keys within the X.509 framework 2

  3. Objectives • Specify how ECC keys and their usage are indicated within X.509 certificates • Simple • Flexible • Generic 3

  4. Today’s Situation • X.509 does not discuss algorithms. • Standards building on X.509 do; e.g.: • PKIX, ECDSA extension to PKIX, • SET • Missing: general, universal way to specify ECC keys within X.509 4

  5. What to specify • Usage of (ECC) keys requires specification of: • certificate signature format • public key format • algorithm type (ECC) • parameters, if any (field, basis, curve, generator) • algorithm (ECDSA, ECDH, MQV, …) • key usage (sign, cert sign, encrypt, …)

  6. Certificate Signature Format • A Certificate contains a signature. • Its format is determined by the signature algorithm chosen for certificate signing. • Proposal: use whatever the standard specifying the certificate signature says. • Caveat: encoding rules

  7. Public Key Format • Public Key format depends on public key type only; is independent of (signature) algorithm. • Proposal: use ECDSA format for any ECC key • Caveat: encoding rules

  8. Algorithm Indicators in X.509 • Subject Public Key Type and Algorithm / Usage are indicated in: • algorithmIdentifier fields • keyUsage extension • extKeyUsage extension • supportedAlgorithms attribute

  9. Algorithm Type and Parameters • Key type (ECC) and system parameters are indicated in algorithmIdentifier • Type: OID for ECC is available via ECDSA • 3 ways of indicating parameters: • by inheritance from CA (omission) • by explicit specification • by reference: OID for a specific parameter set 6

  10. Algorithm Type and Parameters • Proposal: • “Borrow” the parameter specification as in ECDSA and the ECDSA extension to PKIX Certificate Format. • Add OIDs for the standard curves (for the incorporation by reference)

  11. Key Usage • Key usage is indicated through keyUsage and extKeyUsage extensions • No impact specific to ECC • Proposal: no change

  12. Supported Algorithms • Usage: No impact specific to ECC • Required: list of all ECC algorithms (OIDs) supported by the “SECG profile”

  13. Proposals • Key format • As in ECDSA • Signature format • As in signature standard 7

  14. Proposals (cont.) • Algorithm type and parameters: • Borrow algorithmIdentifier OID and specification from ECDSA • Key usage: • No change • Supported Algorithms Attribute • produce list of supported algorithms with OIDs

  15. Summary • Proposals are the wider adoption of an existing (specialized) solutions: • no changes to existing infrastructure; • “compliance” with existing standards; • simple; • flexible.

  16. Roadmap • Formally specify • public key format (see ECDSA) • signature format (encoding rule) • the algorithmIdentifier usage, incl. OID for ECC key type (see ECDSA) • Define OIDs for selected curves • Define OIDs for supported algorithms

  17. Your Input! • Please let us know of any comments, additions, omissions, etc. • Contributions are welcome.