1 Reply by parmstrong3

(7 replies, posted in wolfSSL)

Hi @gojimmypi - we were informed by our commercial contact to email support@wolfssl.com, I'll just send the link to this forum as initial contact

Thanks!

Go to forum: wolfSSL

2 Reply by parmstrong3

(7 replies, posted in wolfSSL)

Ah ... it was the bot stopper.  Since I'm logged in already, I'm not sure why the forum thought I was a bot.

Go to forum: wolfSSL

3 Reply by parmstrong3

(7 replies, posted in wolfSSL)

( this is the third submit of the same information, for some reason my submits are not submitting )

That is extremely valuable information, thanks!

I'm not sure the drastic change in workflow required for us would be something we can work with in the short term.

It sounds like we would have to move from PlatformIO+esp-idf to just esp-idf, which would be easy enough to do, but our entire build process is more PlatformIO based for our production / manufacturing, etc., so our entire workflow would be severely impacted.

We'll see if we can be some kind of solution through our commercial contact at wolfSSL, but it's sounding like this would only be feasible in a longer timeframe than we desire.

Go to forum: wolfSSL

4 Reply by parmstrong3

(7 replies, posted in wolfSSL)

Remember, it's the esp_http_client component above, not esp_xxx_client

Go to forum: wolfSSL

5 Topic by parmstrong3

(7 replies, posted in wolfSSL)

(EDIT: this forum will NOT allow you to use the word "http" since it counts it as a link and there are only three links allowed per message, so, below, replace the letters xxx with h t t p )

We've had a few ESP32 projects using older PlatformIO and the ESP-IDF platform of such, all of which use the esp_xxx_client with the wolfSSL integration instead of bloated mbedtls.

However, in going to the most recent versions (i.e. ESP-IDF v5.2+), we found out that the wolfSSL component was removed, well, not removed, but went to the GPL2.0 version of wolfSSL.  Eventually, we've always gone with the commercial license version of wolfSSL, which has worked great in the past because we simply replace the wolfSSL component with our own, and voila -- working product with the esp_xxx_client.

Also, in relation to esp_xxx_client and with this recent PlatformIO + ESP-IDF v5.2, everything broke in the build, and I've tried various pages such as https://www.wolfssl.com/wolfssl-now-sup … latformio/ to try to get wolfSSL going again with the esp_xxx_client component.  However, since the wolfSSL is actually external to the entire ESP-IDF components, the esp_xxx_client doesn't bring in the wolfSSL library since it's not an ESP-IDF component.

I have set the `build_flags = -DWOLFSSL_USER_SETTINGS, -DWOLFSSL_ESP32` in platformio.ini and yes, I get the library linked in, however esp_xxx_client still uses mbedtls ( probably because of the only way to get the compile going is to use CONFIG_ESP_TLS_USING_MBEDTLS )

Using CONFIG_ESP_TLS_USING_WOLFSSL also fails, because of course, there is no wolfSSL component any more in ESP-IDF.

I'm at a loss to how to get this going, considering wolfSSL is now a foreign entity when it comes to being integrated into ESP-IDF and functionalities of such things as esp_xxx_client

Go to forum: wolfSSL