crypt/wolfssl
1
0
Fork 0
mirror of https://github.com/wolfSSL/wolfssl.git synced 2026-10-24 04:09:07 +03:00
Code Activity

Drop a stale note from the generic SETKEY claim comment

Browse Source 
The comment on a successful WC_SETKEY_AES claim said rounds stays 0
because there is no software key schedule. A callback may now build
one and set rounds, so the comment is cut to the line the ARM32 and
PPC copies use.
This commit is contained in:
Tobias Frauenschläger
2026-10-21 10:44:32 +02:00
parent 6c712d628e
commit 46d11fc6e7
1 changed files with 1 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
wolfcrypt/src/aes.c
View File

@@ -6185,9 +6185,7 @@ static void AesSetKey_C(Aes* aes, const byte* key, word32 keySz, int dir)
(iv != NULL) ? WC_AES_BLOCK_SIZE : 0, dir);
if (cbRet != WC_NO_ERR_TRACE(CRYPTOCB_UNAVAILABLE)) {
if (cbRet == 0) {
/* Callback succeeded - the device owns the key. rounds is
* left at 0: there is no software key schedule, and the
* XTS entry points use that to reject the context. */
/* Callback succeeded - the device owns the key. */
aes->keylen = (int)keylen;
*devOwned = 1;
if (iv != NULL)