mirror of
https://github.com/wolfSSL/wolfssl.git
synced 2026-07-10 23:50:51 +02:00
Daniele Lacamera
9165eb0e4d
Three more config-matrix failures in the AES coverage tests: - Rounds-corruption checks (aes.rounds/cmac.aes.rounds = 0/17 -> expect KEYUSAGE_E) also break under WOLF_CRYPTO_CB_ONLY_AES, which strips the software AES so the op is serviced by the callback and ignores the corrupted struct (same net effect as WOLF_CRYPTO_CB_FIND). Introduce WC_TEST_AES_ROUNDS_OFFLOADED = (WOLF_CRYPTO_CB_FIND || _ONLY_AES), replace the previous WOLF_CRYPTO_CB_FIND-only guards with it, and extend it to the wc_AesEncryptDirect/wc_AesDecryptDirect checks in AesSetKeyArgMcdc (which the ONLY_AES path also offloads). - test_wc_AesFeatureCoverage's GCM-streaming block uses a hardcoded 256-bit key; guard it with WOLFSSL_AES_256 (failed under -DNO_AES_256). - Its AES-KeyWrap block uses a 192-bit key; guard with WOLFSSL_AES_192 (failed under -DNO_AES_192). Verified: --enable-swdev --enable-cryptocb ... -DWOLF_CRYPTO_CB_ONLY_AES and --enable-all -DNO_AES_192 -DNO_AES_256 now both build and pass; a normal --enable-all build still runs the rounds checks.
Before creating any new configure files (.conf) read the CONF_FILES_README.md