Choice of parameter for certificate APIs ?
Posted: Tue Jan 07, 2020 5:17 pm
Hi,
As you may have noticed (see viewtopic.php?f=2&t=13716) I am working on certificate stuff.
Why do the esp32 APIs work with a certificate in PEM format instead of the (e.g.) mbedtls_x509_crt * ?
If you use more than one module that requires this, then the all the conversions will happen multiple times. Looks unnecessary. An example is esp_https_ota(). Shouldn't functions like that have a
as one of the fields in the esp_http_client_config_t parameter, instead of
Small addition to my post : I can find "_pem" in these include files (excluding components/mbedtls) :
Thanks,
Danny
As you may have noticed (see viewtopic.php?f=2&t=13716) I am working on certificate stuff.
Why do the esp32 APIs work with a certificate in PEM format instead of the (e.g.) mbedtls_x509_crt * ?
If you use more than one module that requires this, then the all the conversions will happen multiple times. Looks unnecessary. An example is esp_https_ota(). Shouldn't functions like that have a
Code: Select all
const mbedtls_x509_crt *certificateCode: Select all
const char *cert_pemCode: Select all
components/esp_https_ota/include/esp_https_ota.h
components/mqtt/esp-mqtt/include/mqtt_client.h
components/esp_http_client/include/esp_http_client.h
components/esp_https_server/include/esp_https_server.h
components/esp-tls/esp_tls.h
Danny