ESP32 Forum

^_^
In the spirit of full disclosure, I'm currently working on a fork of the project to make an Amazon Alexa client, and have progressed to a stage where SSL via mbedtls and HTTP/2 via nghttp2 works. TODOs are I2S microphone input (via InvenSense ICS-43434) and communication with the Amazon Alexa backend, which I'm currently protoyping in Java.
Not sure if that warrants one of your boards...

BuddyCasino wrote:^_^
In the spirit of full disclosure......

Jakobsen wrote:Hi Buddy
O yes - need more coffee - i did commit - as I use to on SVN but i see there is more to it then that.
I will try to follow you description tonight and have added git to my bucket list.
Thanks /j

Any progress on this? Thinking about building myself a little MP3 streamer/player

Hi Jimmy
No sorry - was hit by work. But just get going - the code works out the box - mono. There is still room for improvement on the UX part of the code. /j

Haven't gotten to that part yet, I'm just realizing that C pointers can be tougher than I thought and kinda stuck in a refactoring.

I chose mbedtls because its the native API for the ESP32 (OpenSSL is just wrapping it and nt completely implemented), and using nghttp I had to implement the I/O parts all by myself anyway. Its actually not that hard.

If you want to verify the server certificate, then yes you need to have the appropriate root cert in memory somewhere. If not, you can simply ignore it. I haven't seen a generic lib that comes with all of the common CAs and automatically picks the right one, but if it exists I'd be happy to learn about it.

I need HTTP2 because I'm building an Amazon Alexa client, and thats all they offer.

Its going to be on Github as soon as I got it to work.

Might help with apll

https://esp32.com/viewtopic.php?f=2&t=8 ... t=10#p5869

BuddyCasino wrote:Its going to be on Github as soon as I got it to work.

we did it in the meantime

Thats ok. I won't fret.