Problem with importKey method about isomorphic-webcrypto HOT 4 CLOSED

Update...getting this in msrcrypto:

'actual:', [ 65, 37, 151, 233, 143, 164, 114, 135, 254, 114, 31, 115, 142, 170, 92, 163 ], ' expected: ', { name: 'keyData', type: 'Object', required: true }. msrcrypto is apparently looking for a key in jwk format.

from isomorphic-webcrypto.

So I generated a jwk key for testing purposes and was eventually able to see that PBKDF2 is not supported. This is unfortunate for our case as we are locked into using PBKDF2. So for now it's necessary for me to explore the other option available to us - namely using a hidden web view to get access to window.crypto inside react-native. Unfortunately this makes it hard for me to spend time on a PR at this stage, but I will provide a list of the functions I was hoping to add to the demo project - the ones that we needed: importKey(), exportKey(), exportPrivateKey(), deriveKey(), generateKey(). Hope that's vaguely useful. And of course, if PBKDF2 ever gets supported in msrcrypto, I would definitely prefer this approach.

from isomorphic-webcrypto.

No worries. We're unlikely to see any movement on msrcrypto from Microsoft (it's been dormant since 2015), but I'll add a table that shows what's supported in each environment to prevent this sort of trouble in the future. Thanks for digging in.

from isomorphic-webcrypto.

Hi from 2019, isomorphic-webcrypto should now work with "PBKDF2" in importKey and deriveBits

from isomorphic-webcrypto.