mirror of
https://github.com/wolfSSL/wolfssl.git
synced 2026-10-24 04:09:07 +03:00
edb6f7156b
The ARM32 and PPC asm wc_AesSetKey only ran the crypto callback block when aes->devId was set. With WOLF_CRYPTO_CB_FIND a find callback can map an INVALID_DEVID object onto a device, and the AES encrypt paths already dispatch such objects to it, but the key was never offered to a SETKEY device or copied into devKey. The device then ran on a key it never saw. Skip the devId check under WOLF_CRYPTO_CB_FIND, as the generic wc_AesSetKey already does. test_wc_CryptoCb_Aes_SetKey_Find maps INVALID_DEVID onto a key-owning device and checks that wc_AesSetKey and wc_AesSetKeyDirect both offer it the key.
Before creating any new configure files (.conf) read the CONF_FILES_README.md