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

Possibility of data corruption when utilizing multiple encryption keys #3017

Closed
ramonsmits opened this issue Oct 19, 2015 · 1 comment
Closed
Assignees
Labels

Comments

@ramonsmits
Copy link
Member

Most of the time, attempting to decrypt a message with an incorrect key will throw an exception. However, there is a small possibility (less than 0.4%) that we decrypt a message with an alternate key, and while the resulting message would not make sense, no exception is thrown. This is because we iterate through the available keys and try to decrypt with each one. When decryption fails, we continue using the next available key. If decryption succeeds using the incorrect key then the data that is decrypted is corrupt.

@ramonsmits
Copy link
Member Author

Fixed in 3.3.17, 4.7.8, 5.0.7, 5.1.5, 5.2.9

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

No branches or pull requests

1 participant