WebCrypto opaque/extractable keys?

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript

Research direction

Start with the linked MDN SubtleCrypto.generateKey documentation and compare the extractable parameter with the Web Platform and native use cases described here. Review how IndexedDB is used in the stated opacity model. Done means reaching and documenting a clear WinterCG position on whether non-extractable keys should be supported.

Written by the indexing model from the issue text.

Description

When creating a key in WebCrypto, the extractable parameter/property indicates whether a key should be treated as opaque. This makes sense on the Web Platform where you could put something in IndexedDB and read it back out without compromising opacity, but makes less sense natively--how would it be used? Should WinterCG platforms be expected to support non-extractable keys?

Dominant language
Bikeshed
Stars
308
Forks
17
PR merge metrics
No merged PRs in 30d

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.

More from WinterTC55/proposal-minimum-common-api

All issues in WinterTC55/proposal-minimum-common-api

Similar issues

More Cryptography issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.