fix: add error handling in decryptBytes to throw CryptoFailedException for AEADBadTagException #739
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Improves error handling for cryptographic operations by adding specific handling for
AEADBadTagException. This exception occurs during AES-GCM decryption when the authentication tag verification fails, indicating possible data corruption or tampering.currently unhandled: #730
Changes
javax.crypto.AEADBadTagExceptioninCipherStorageBaseCryptoFailedExceptionto@ThrowsannotationError Message Changes
Previous generic error handling is now replaced with a specific message for authentication failures:
"Decryption failed: Authentication tag verification failed. This usually indicates that the encrypted data was modified, corrupted, or is being decrypted with the wrong key."
Only improves error handling and messaging.