[javascript] Switch to WebCrypto API #1166
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
arjunyel
force-pushed
the
webcrypto-api
branch
from
fcc02bf
to
2615fe6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Edge runtimes like Cloudflare Workers bill based on on milliseconds of CPU time which means its important for cryptography operations to use the WebCrypto API. Also one less dependency :D
Solution
Replaced
fast-sha256with the WebCrypto API.Breaking changes:
Now requires the environment to have the WebCrypto API available. Its enabled by default on Node LTS and can be easily polyfilled in older environments.
Both
signandverifyare now asyncBased on #1163