Files
wolfssl/tests/swdev/user_settings.h
T
rizlik c5ef060139 WOLF_CRYPTO_CB_ONLY_AES: add support + swdev for testing
Modes (CTR, GCM, CCM, etc.) can be supported either directly or fallback
to invoking the crypto callback with a "direct" (ECB) mode.
Software implementation and AES tables are stripped under CB_ONLY_AES.

wc_swdev gains AES support so WOLF_CRYPTO_CB_ONLY_AES builds can be
tested.

crypto find cb support added to wc_AesSetKey in order to support current
CI tests that use INVALID_DEVID.
2026-05-13 16:18:52 +02:00

26 lines
1020 B
C

/* tests/swdev/user_settings.h -- settings for wc_swdev.
*
* The swdev software backend must stay ABI-identical to the main library:
* every wolfCrypt struct that crosses the cryptocb boundary (wc_Sha256,
* Aes, RsaKey, ecc_key, ...) is allocated by one compilation and used by
* the other. The only macros that may differ between the two compilations
* are the WOLF_CRYPTO_CB_ONLY_* gates below -- those strip the software
* implementations from the main library so every operation routes through
* the crypto callback; swdev needs the software paths intact. Every other
* setting is inherited from wolfssl/options.h so layouts stay in sync. */
#ifndef WC_SWDEV_USER_SETTINGS_H
#define WC_SWDEV_USER_SETTINGS_H
#include <wolfssl/options.h>
#undef WOLF_CRYPTO_CB_ONLY_RSA
#undef WOLF_CRYPTO_CB_ONLY_ECC
#undef WOLF_CRYPTO_CB_ONLY_SHA256
#undef WOLF_CRYPTO_CB_ONLY_AES
#ifndef WOLF_CRYPTO_CB
#error "wc_swdev requires the main build to define WOLF_CRYPTO_CB"
#endif
#endif /* WC_SWDEV_USER_SETTINGS_H */