AuroraMiddleware/mbedtls
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Adds comments for clarification

Browse Source 
Adds two comments to clarify 1) why an offset is used
in the call to psa_aead_verify() and 2) why the test of
.hits_finish is always 0 in this test case.

Signed-off-by: Thomas Daubney <thomas.daubney@arm.com>
This commit is contained in:
Thomas Daubney 2022-04-22 11:36:07 +01:00
parent 7435d2d08e
commit 7d063f6467
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
tests/suites/test_suite_psa_crypto_driver_wrappers.function
View File

@ -2521,6 +2521,8 @@ void aead_decrypt_setup( int key_type_arg, data_t *key_data,
TEST_EQUAL( mbedtls_test_driver_aead_hooks.hits_update,
forced_status == PSA_SUCCESS ? 1 : 0 );
/* Offset applied to output_data in order to handle cases where verify()
* outputs further data */
PSA_ASSERT( psa_aead_verify( &operation, output_data + output_length,
output_size - output_length,
&verify_output_length, input_tag->x,
@ -2529,6 +2531,8 @@ void aead_decrypt_setup( int key_type_arg, data_t *key_data,
TEST_EQUAL( mbedtls_test_driver_aead_hooks.hits_verify,
forced_status == PSA_SUCCESS ? 1 : 0 );
/* Since this is a decryption operation,
* finish should never be hit */
TEST_EQUAL( mbedtls_test_driver_aead_hooks.hits_finish, 0 );
TEST_EQUAL( mbedtls_test_driver_aead_hooks.hits_abort,