w3c / w3c/webcrypto

Deterministically derive key pair from secret, salt, and context?

Open
#254 0 comments 2 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

To implement (message layer security)[https://github.com/mlswg/mls-protocol/blob/main/draft-ietf-mls-protocol.md] in the browser, a client needs to be able to derive a key pair from a secret, salt, and context, e.g. something like this:

window.crypto.subtle.deriveKey(
      {
        name: "HKDF",
        hash: {name: "SHA-512"},
        salt: salt,
        info: context
      },
      secret,
      {name: "ECDSA", namedCurve: "P-384"},
      true,
      ["sign", "verify"]);

Could this be added to the spec?

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

Review the Message Layer Security protocol draft linked in the issue alongside the Web Cryptography API specification. Determine whether deterministic key-pair derivation belongs in the API and what requirements the proposed operation would need; done means a documented specification decision or a concrete proposal accepted by maintainers.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, cryptography, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.