Add support for encrypted communications using BearSSL
Simple testing already works using some of the ESP8266 examples, but no detailed testing yet done
TODO:
[X] WiFiClientSecure/WiFiServerSecure porting
[X] BearSSL porting
[X] NTP integration (since certs have not-valid-before/after
[X] CertStore integration
[X] Platform.IO update
[X] Enable secondary stack for BearSSL
[X] Testing^4
[X] Examples
[X] Docs
Fixes #679 , extension of #670
@brentru sure, if you're prepared to do a little debugging if things go bad. The PR right now seems very functional 🤞 (all the examples "just worked") and you can just check out the bssl branch and run (make sure to git submodule update --init of course since there is a new library). Be aware this is exactly like the ESP8266 SSL stuff, so you'll need to use client->setInsecure() or install valid server public certs to connect). Client certs should work, too, but I have not yet messed with it.
@brentru sure, if you're prepared to do a little debugging if things go bad. The PR right now seems very functional :crossed_fingers: (all the examples "just worked") and you can just check out the `bssl` branch and run (make sure to `git submodule update --init` of course since there is a new library). Be aware this is exactly like the ESP8266 SSL stuff, so you'll need to use `client->setInsecure()` or install valid server public certs to connect). Client certs should work, too, but I have not yet messed with it.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Add support for encrypted communications using BearSSL
Simple testing already works using some of the ESP8266 examples, but no detailed testing yet done
TODO:
[X] WiFiClientSecure/WiFiServerSecure porting
[X] BearSSL porting
[X] NTP integration (since certs have not-valid-before/after
[X] CertStore integration
[X] Platform.IO update
[X] Enable secondary stack for BearSSL
[X] Testing^4
[X] Examples
[X] Docs
Fixes #679 , extension of #670
@earlephilhower Are you interested in someone to test against a secure MQTT broker when this PR is ready?
@brentru sure, if you're prepared to do a little debugging if things go bad. The PR right now seems very functional 🤞 (all the examples "just worked") and you can just check out the
bsslbranch and run (make sure togit submodule update --initof course since there is a new library). Be aware this is exactly like the ESP8266 SSL stuff, so you'll need to useclient->setInsecure()or install valid server public certs to connect). Client certs should work, too, but I have not yet messed with it.