You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It may be a not-often-used compiler path, but it seems that the commit 8bb6ff8 could have introduced an issue here:
static int InitSha384(wc_Sha384* sha384)
{
....
esp_sha_hw_unlock(&(sha512->ctx));
....
the only variable defined at this point is sha384 (which looks OK by the name of the function).
With the obvious patch it compiles this file OK:
@ wolfcrypt/src/sha512.c:1309 @ static int InitSha384(wc_Sha384* sha384)
sha384->ctx.isfirstblock = 1;
if(sha384->ctx.mode == ESP32_SHA_HW) {
/* release hw */
- esp_sha_hw_unlock(&(sha512->ctx));
+ esp_sha_hw_unlock(&(sha384->ctx));
}
/* always set mode as INIT
* whether using HW or SW is determined at first call of update()
What do you think ? Could it be a typo, or did I miss some configuration somewhere ?
Contact Details
No response
Version
tag
v5.5.4-stable
ormaster
Description
Compiling OVMSv3 for ESP-IDF version 5+ (NOT using the component integration (https://github.com/espressif/esp-wolfssl/)).
It may be a not-often-used compiler path, but it seems that the commit 8bb6ff8 could have introduced an issue here:
the only variable defined at this point is
sha384
(which looks OK by the name of the function).With the obvious patch it compiles this file OK:
What do you think ? Could it be a typo, or did I miss some configuration somewhere ?
Reproduction steps
No response
Relevant log output
The text was updated successfully, but these errors were encountered: