You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Revert to not using the WebCrypto for X25519 (reverting part of #1782): due to missing support in WebKit and Chrome (without experimental flags), and issues in Firefox v130+ (resulting in errors on decryption and key generation), for now we go back to using a JS implementation.
NB: this change only affects encryption and decryption using X25519. For signing and verification using Ed25519 we keep relying on
WebCrypto when available (namely in WebKit, Firefox, and Node).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
What's Changed
Revert to not using the WebCrypto for X25519 (reverting part of #1782): due to missing support in WebKit and Chrome (without experimental flags), and issues in Firefox v130+ (resulting in errors on decryption and key generation), for now we go back to using a JS implementation.
NB: this change only affects encryption and decryption using X25519. For signing and verification using Ed25519 we keep relying on
WebCrypto when available (namely in WebKit, Firefox, and Node).
Full Changelog: v6.0.0-beta.3.patch.0...v6.0.0-beta.3.patch.1
For more context about the crypto-refresh changes introduced by OpenPGP.js v6, refer to the changelog of the initial prerelease.
This discussion was created from the release v6.0.0-beta.3.patch.1.
Beta Was this translation helpful? Give feedback.
All reactions