[feature request] importing SPKI from X.509 Certificates
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 294
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
I wish Web Crypto API could deal with importing the SPKI from X.509 Certificates.
This could either be an extension to the existing SPKI import steps tied to the spki KeyFormat, or a totally new import-only step x509 KeyFormat.
The import format steps for x509 are simple, extract the SPKI out of the passed in X.509 BufferSource and call importKey with spki as the format.
Reason is simple, dealing with X.509 for the simple purpose of validating signatures requires a lot of brittle javascript to get right and the Web Crypto API runtimes already have the ability to deal with X.509, it should not be a big deal and would simplify developer's job a lot.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Web Crypto API's existing SPKI import steps and the proposed x509 KeyFormat approach described in the issue. Determine which import design the specification should adopt, then define completion as an agreed specification change that extracts the SPKI from an X.509 BufferSource for signature validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cryptography, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100