crypto/x509: support certificates with X25519 public keys #70642

EdSchouten · 2024-12-02T18:09:09Z

Even though X25519 can't be used for signing, it may be desirable to use
a CA structure to sign X25519 keys that are used for ECDH purposes. This
change adds the ability to properly extract X25519 public keys from
certificates that contain such keys. It also makes it possible to create
such certificates through CreateCertificate().

Even though X25519 can't be used for signing, it may be desirable to use a CA structure to sign X25519 keys that are used for ECDH purposes. This change adds the ability to properly extract X25519 public keys from certificates that contain such keys. It also makes it possible to create such certificates through CreateCertificate().

gopherbot · 2024-12-02T18:16:04Z

This PR (HEAD: e65cf75) has been imported to Gerrit for code review.

Please visit Gerrit at https://go-review.googlesource.com/c/go/+/632875.

Important tips:

Don't comment on this PR. All discussion takes place in Gerrit.
You need a Gmail or other Google account to log in to Gerrit.
To change your code in response to feedback:
- Push a new commit to the branch used by your GitHub PR.
- A new "patch set" will then appear in Gerrit.
- Respond to each comment by marking as Done in Gerrit if implemented as suggested. You can alternatively write a reply.
- Critical: you must click the blue Reply button near the top to publish your Gerrit responses.
- Multiple commits in the PR will be squashed by GerritBot.
The title and description of the GitHub PR are used to construct the final commit message.
- Edit these as needed via the GitHub web interface (not via Gerrit or git).
- You should word wrap the PR description at ~76 characters unless you need longer lines (e.g., for tables or URLs).
See the Sending a change via GitHub and Reviews sections of the Contribution Guide as well as the FAQ for details.

gopherbot · 2024-12-02T18:24:53Z

Message from Gopher Robot:

Patch Set 1:

(1 comment)