Skip to content
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

[Question] Updating to v3.0.0 - breaking changes. #99

Open
GamerMedic opened this issue Feb 16, 2024 · 1 comment
Open

[Question] Updating to v3.0.0 - breaking changes. #99

GamerMedic opened this issue Feb 16, 2024 · 1 comment

Comments

@GamerMedic
Copy link

I know that v3.0.0 has breaking changes. It does mean that my encrypted data can't be read using newer version, is it possible to update and be able to decrypt the already encrypted data?

Or do I need to decrypt all of the data that I have, update, and then encrypt using the updated version?

@paragonie-security
Copy link
Contributor

The changes between versions was with the code, not the cryptography. They were API changes, not message format changes. Old data can still be decrypted.

However, the ModernCrypto backend has been deprecated and you should use BoringCrypto instead (which provides multi-tenant security).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants