cuberite/polarssl
1
0
Fork 0
mirror of https://github.com/cuberite/polarssl.git synced 2025-09-29 00:18:06 -04:00
Code Issues Packages Projects Releases Wiki Activity

Test calling complete() after {sign|verify}_hash_start fails

Browse Source 
Signed-off-by: Paul Elliott <paul.elliott@arm.com>
This commit is contained in:
Paul Elliott 2023-02-27 09:53:08 +00:00
parent 17152df58d
commit 587e780812
1 changed files with 28 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
tests/suites/test_suite_psa_crypto.function
View File

@ -6662,6 +6662,12 @@ exit:
* 3. Test that the number of ops done prior to start and after abort is zero * 3. Test that the number of ops done prior to start and after abort is zero
* and that each successful stage completes some ops (this is not mandated by * and that each successful stage completes some ops (this is not mandated by
* the PSA specification, but is currently the case). * the PSA specification, but is currently the case).
*
* 4. Check that calling complete() when start() fails and complete()
* after completion results in a BAD_STATE error.
*
* 5. Check that calling start() again after start fails results in a BAD_STATE
* error.
*/ */
void sign_hash_fail_interruptible(int key_type_arg, data_t *key_data, void sign_hash_fail_interruptible(int key_type_arg, data_t *key_data,
int alg_arg, data_t *input_data, int alg_arg, data_t *input_data,
@ -6718,6 +6724,15 @@ void sign_hash_fail_interruptible(int key_type_arg, data_t *key_data,
TEST_EQUAL(actual_status, expected_start_status); TEST_EQUAL(actual_status, expected_start_status);
if (expected_start_status != PSA_SUCCESS) { if (expected_start_status != PSA_SUCCESS) {
/* Emulate poor implementation, and call complete anyway, even though
* start failed. */
actual_status = psa_sign_hash_complete(&operation, signature,
signature_size,
&signature_length);
TEST_EQUAL(actual_status, PSA_ERROR_BAD_STATE);
/* Test that calling start again after failure also causes BAD_STATE. */
actual_status = psa_sign_hash_start(&operation, key, alg, actual_status = psa_sign_hash_start(&operation, key, alg,
input_data->x, input_data->len); input_data->x, input_data->len);
@ -7183,6 +7198,12 @@ exit:
* 3. Test that the number of ops done prior to start and after abort is zero * 3. Test that the number of ops done prior to start and after abort is zero
* and that each successful stage completes some ops (this is not mandated by * and that each successful stage completes some ops (this is not mandated by
* the PSA specification, but is currently the case). * the PSA specification, but is currently the case).
*
* 4. Check that calling complete() when start() fails and complete()
* after completion results in a BAD_STATE error.
*
* 5. Check that calling start() again after start fails results in a BAD_STATE
* error.
*/ */
void verify_hash_fail_interruptible(int key_type_arg, data_t *key_data, void verify_hash_fail_interruptible(int key_type_arg, data_t *key_data,
int alg_arg, data_t *hash_data, int alg_arg, data_t *hash_data,
@ -7235,6 +7256,13 @@ void verify_hash_fail_interruptible(int key_type_arg, data_t *key_data,
TEST_EQUAL(actual_status, expected_start_status); TEST_EQUAL(actual_status, expected_start_status);
if (expected_start_status != PSA_SUCCESS) { if (expected_start_status != PSA_SUCCESS) {
/* Emulate poor implementation, and call complete anyway, even though
* start failed. */
actual_status = psa_verify_hash_complete(&operation);
TEST_EQUAL(actual_status, PSA_ERROR_BAD_STATE);
/* Test that calling start again after failure also causes BAD_STATE. */
actual_status = psa_verify_hash_start(&operation, key, alg, actual_status = psa_verify_hash_start(&operation, key, alg,
hash_data->x, hash_data->len, hash_data->x, hash_data->len,
signature_data->x, signature_data->x,