You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi I have a question about the implementation of AesCbc:
I see that the result of encryption is prefixed with the iv and the decryption, instead, removes the iv decrypting.
Is that a reason for this? from the RFC or usage examples of the Cipher dont do anything similar.
The purpose of this design is to facilitate encryption and decryption without requiring the user to understand the process of generating iv (BTW, iv also supports customization), it also refers to the design of Tink. AesSiv.java#L125, AesCtrJceCipher.java#L95 🍺
Hi I have a question about the implementation of
AesCbc
:I see that the result of encryption is prefixed with the
iv
and the decryption, instead, removes theiv
decrypting.Is that a reason for this? from the RFC or usage examples of the
Cipher
dont do anything similar.Even the tests vectors from https://datatracker.ietf.org/doc/html/rfc3602#section-4 the cipher does not include the
iv
and the assertions you implemented need to modify the result to match the test vectors.Thanks for that!
The text was updated successfully, but these errors were encountered: