w3c / w3c/webcrypto

Allow creating hedged EdDSA signatures?

Open
#424 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
294
Forks
78
PR merge metrics
No merged PRs in 30d

Description

The current specification of EdDSA, in RFC 8032 (which we refer to), defines Ed25519 and Ed448 as being deterministic.

WebKit's implementation of Ed25519, when using macOS's CryptoKit, produces hedged (non-deterministic) signatures as per draft-irtf-cfrg-det-sigs-with-noise, citing security benefits.

So, we may want to allow this as well in the spec.


This is a copy of https://github.com/WICG/webcrypto-secure-curves/issues/28, to keep track of that issue after we archive WICG/webcrypto-secure-curves.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the EdDSA requirements in RFC 8032 and the linked draft-irtf-cfrg-det-sigs-with-noise. Compare those requirements with the current Web Cryptography API specification, then define what allowing hedged Ed25519 and Ed448 signatures would require; the issue does not name implementation files or tests.

Written by the indexing model from the issue text.

Assessment

Domain
api, cryptography
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.