Advanced Users can post their questions and comments here for the not so Newbie crowd.

Moderator: eriksl

User avatar
By davydnorris
#82219 No changes to lwIP - it's a layer above, but we are talking SSL and crypto... do you even need to ask about memory?? Haha

Being serious, any crypto is expensive - both in terms of CPU and memory. But later SDKs have done it well, so I know you will do it better!
User avatar
By davydnorris
#82220
eriksl wrote:Yeah I see the consideration here.

What's your experience with mbedtls? I've never used it (never need it...). Is it easy to use on top of an existing LWIP implementation or does it need changes in LWIP? What's the memory footprint (my greatest concern)?


So today I got the current lib working in the NonOS environment, with stubs for networking. Right now my chip thinks it's connecting and is doing the right things.

Still to do the espconn layer...
User avatar
By davydnorris
#82316 Just about - I'll let you know when I've got it completely done.

I've just pulled the very latest commit from the ESP32 IDF - it's different from both the ESP8266 RTOS and the stand alone new MQTT (and the tuanpm version!).

Wish they would just create a single version and pull each OS's dist from there!