Introduce SSLClient library based on WiFiClientSecure and rework WiFiClientSecure to use it #6054
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR reworks WiFiClientSecure into SSLClient so that it can be used with any Client-derived class.
Then it goes on to modify WiFiClientSecure to work with SSLClient in conjunction with a normal WiFiClient.
The PR was tested with ESP32 WiFi as well as with a GSM module supported by TinyGSM.
Impact
Any Client-derived class can get SSL applied to it, e.g. WiFiClient, but also TinyGsmClient and any other clients.
Protocol Clients can then be put on top of SSL, e.g. PubSubClient or ArduinoHttpClient.
This may also allow for DTLS to be supported as well in the same style in the future, e.g. CoAP over both WiFi and GSM, etc.