Opened 5 years ago

Closed 5 years ago

#189 closed enhancement (fixed)

Permit logs to use EdDSA

Reported by: rob.stradling@… Owned by: draft-ietf-trans-rfc6962-bis@…
Priority: major Milestone: review
Component: rfc6962-bis Version:
Severity: - Keywords:
Cc:

Description

The specification for EdDSA was published as RFC8032 a few months ago. The advantages of EdDSA over ECDSA are summarized at https://tools.ietf.org/html/rfc8032#section-1

We should add one or more of the EdDSA Instances to the Signature Algorithms registry.

Expert advice on which of the EdDSA Instances to add would be appreciated.

Change History (3)

comment:1 Changed 5 years ago by eranm@…

From what I understand (consulting with a few Google engineers who actually know crypto), EdDSA is supported in BoringSSL and there's no reason not to support it in 6962-bis.

comment:2 Changed 5 years ago by rob.stradling@…

  • Milestone set to review

Addressed by https://github.com/google/certificate-transparency-rfcs/commit/7ed2a968743f9e715812eab1ed9eae582827ac4e

This adds Ed25519 (PureEdDSA with the edwards25519 curve) to the 6962-bis signature algorithm registry.

Also, as per discussion on the list, we briefly considered switching the RSA requirement from PKCS#1v1.5 to RSA-PSS, but we've ultimately decided to drop RSA support altogether.

comment:3 Changed 5 years ago by melinda.shore@…

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.