Builds with accelerated SHA3 still include the built-in implementation #542

Closed
opened 2025-10-22 05:14:11 -05:00 by gilles-peskine-arm · 0 comments
gilles-peskine-arm commented 2025-10-22 05:14:11 -05:00 (Migrated from github.com)

The code in sha3.c and test_suite_shax.* uses PSA_WANT_ALG_SHA3_xxx as compilation guards. As a result, both will be included in the build even if SHA3 is fully accelerated.

Applies to TF-PSA-Crypto 1.0. It's ok in 3.6.

The goal of this issue is to fix this: if SHA3 is accelerated, sha3.o must be empty. Assert this in component_test_accel_hash in components-configuration-crypto.sh.

The code in `sha3.c` and `test_suite_shax.*` uses `PSA_WANT_ALG_SHA3_xxx` as compilation guards. As a result, both will be included in the build even if SHA3 is fully accelerated. Applies to TF-PSA-Crypto 1.0. It's ok in 3.6. The goal of this issue is to fix this: if SHA3 is accelerated, `sha3.o` must be empty. Assert this [in `component_test_accel_hash` in `components-configuration-crypto.sh`](https://github.com/Mbed-TLS/TF-PSA-Crypto/pull/586#discussion_r2615123148).
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
gh-Mbed-TLS/TF-PSA-Crypto#542
No description provided.