-
Notifications
You must be signed in to change notification settings - Fork 26
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
Cannot export RSA-OAEP key on iOS 10 Safari #53
Comments
This is because Safari can generate RSA-OAEP but have error on We can replace native |
If I understand correctly the issue is Safari, or this version, does not allow exporting if the public key for RSA-OAEP? This seems pretty fundamental, isn’t there a a chance we have to make this call in a different way in the case if Safari? Does WebCrypto-tests have the same behavior? |
Sounds like Safari 11 works but this version does not. If so then yes using JS is the right solution but only for those older than 11. |
Yes, I can confirm it works on iOS 11 In fact the reason I started researching an alternative to the native WebCrypto api in the first place was because my app which works perfectly fine on iOS 11 suddenly stopped working on iOS 10. This meant I can't use native webcrypto for exporting, so I started looking and i came across this project. |
@doraemondrian Can you try https://microshine.github.io/test-webcrypto/ on Safari v10 and v11? |
@microshine here it is: iOS 10 on iPad
iOS 11 on iPhone
|
@doraemondrian I'll update importKey for RSA-OAEP and publish new version |
Thanks! Looking forward to it! |
I published v0.1.34 |
I took the same example over at #50 and just switched the AES-GCM algorithm to RSA-OAEP, and that seems to break the example.
By the way I can confirm that the original example (after the fix at #50 (comment)) works just fine.
It just doesn't work for RSA-OAEP export.
Here's the code (Pretty much the same, except I'm trying to export an RSA key)
I get an
"Y3 error: Error: Cannot export native CryptoKey from JS implementation"
.I'm using iOS 10 safari on an iPad. (It works fine on other browsers)
The text was updated successfully, but these errors were encountered: