Open ruidazeng opened 5 days ago
There some notes on the design decisions here: doc/webcrypto-parity.md.
It something we could reconsider before declaring the API stable with a 1.0.0
release.
Personally, I'm not sure we need it, we could perhaps get away with documenting how to implement deriveKey
using deriveBytes
and importRaw
. Perhaps we can even have tests to ensure that such an implementation is compatible with the behavior the browser has.
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.