fix: validate key length in symmetricDecrypt#2
Conversation
…rypt The symmetricDecrypt method was previously only logging a debug message when an invalid key length (!= 32 bytes) was provided, which could lead to errors later in execution. This change moves the validation check alongside the existing null checks before the try block, throwing an IllegalArgumentException immediately if the key length is invalid. Co-authored-by: SirDank <52797753+SirDank@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
The
symmetricDecryptmethod inCryptoHelper.javawas previously only logging a debug message when an invalid key length (!= 32 bytes) was provided, but continued with the invalid key length.This change:
IllegalArgumentExceptiontryblock alongside the other argument validationsPR created automatically by Jules for task 13064811098211674903 started by @SirDank