-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for deriveKey Method in Key Derivation Algorithms #173
Comments
There some notes on the design decisions here: doc/webcrypto-parity.md. It something we could reconsider before declaring the API stable with a Personally, I'm not sure we need it, we could perhaps get away with documenting how to implement |
Filed #188 to explore if this is necessary or not. I'm leaning towards the idea that we need a tutorial for how to do Because adding direct support for
|
See also discussion in #53 |
These makes sense to me. Are there any arguments for why this might not be necessary? |
Enable support for the
deriveKey
method for key derivation algorithms, including ECDH, HKDF, and PBKDF2, overderivedBits
. This approach allows for direct derivation of cryptographic keys from a base key and specified algorithm parameters, returning aCryptoKey
object ready for immediate use. This implementation would more closely align with the Web Cryptography API specification.The text was updated successfully, but these errors were encountered: