Updated library log tracing arguments to match expected data types
The gcc-extensa compiler in IDF 5 is much more strict and fails if the arguments to log functions (which use VA ARGS) are incompatible with the format string.
Update azure_iot_jws_mbedtls.c to work with MBED-TLS v3
To provide compatibility of the ADU JWS code to both mbed-tls v2 and v3 (and also to better comply with RFC 3447
https://www.rfc-editor.org/rfc/rfc3447#section-5.1.2), function mbedtls_rsa_pkcs1_verify is now used instead of
mbedtls_rsa_pkcs1_decrypt since the device has only access to the public key.
Tested all ESP32 samples (esp32, azureiotkit, adu) using ESP-IDF versions 4.4.3 and 5.
ewertons
commented
1 year ago
Updated library log tracing arguments to match expected data types The gcc-extensa compiler in IDF 5 is much more strict and fails if the arguments to log functions (which use VA ARGS) are incompatible with the format string.
Update azure_iot_jws_mbedtls.c to work with MBED-TLS v3
Please see this for the differences between mbed-tls v2 and v3: https://github.com/Mbed-TLS/mbedtls/blob/development/docs/3.0-migration-guide.md#remove-the-mode-parameter-from-rsa-functions
To provide compatibility of the ADU JWS code to both mbed-tls v2 and v3 (and also to better comply with RFC 3447 https://www.rfc-editor.org/rfc/rfc3447#section-5.1.2), function mbedtls_rsa_pkcs1_verify is now used instead of mbedtls_rsa_pkcs1_decrypt since the device has only access to the public key.
Tested all ESP32 samples (esp32, azureiotkit, adu) using ESP-IDF versions 4.4.3 and 5.