fix: align OCB3 decrypt length checks with encrypt #774
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.
Previously OCB3 decryption accepted plaintext and associated data of exactly max_len bytes, which could lead to out-of-bounds access in the precomputed L table and a panic instead of a clean error for boundary-size inputs.
Tightened the max_len checks in decrypt_inout_return_tag to match encryption, rejecting inputs with length >= max_len for both plaintext and associated data so that large inputs consistently return an error instead of panicking.