aboutsummaryrefslogtreecommitdiffstats
path: root/tests/checkasm/checkasm.c
diff options
context:
space:
mode:
authorJames Almer <jamrial@gmail.com>2025-04-03 17:40:35 -0300
committerJames Almer <jamrial@gmail.com>2025-04-05 20:46:40 -0300
commit19085287b49de6c6f6a589a4bfddafa82aa58afb (patch)
treec8cba69d322420eeca5b14a8e38a553cbad7e0b3 /tests/checkasm/checkasm.c
parent0a34f009aaf41ff72c0489858962d9e2102d1977 (diff)
downloadffmpeg-19085287b49de6c6f6a589a4bfddafa82aa58afb.tar.gz
avutil/tests/aes_ctr: also check the encrypted buffer
The test in its current form is just ensuring the plain text output is the same as the plain text input, not bothering to check if anything was done with the latter. av_aes_ctr_crypt() could be a simple memcpy under the hood and this test would still succeed. To check the integrity of the encrypted buffer, both the IV and the key need to be fixed. As such, and in order to not remove the existing randomization of the input IV, do two runs, one with random initialization data, and one with static data. Signed-off-by: James Almer <jamrial@gmail.com>
Diffstat (limited to 'tests/checkasm/checkasm.c')
0 files changed, 0 insertions, 0 deletions