You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hardware: ESP-12F
Core Version: github commit 7b09ae5 Nov 22 2017
Description
ESP8266httpUpdate supports https, which is great, but it appears I have to hardcode the fingerprint of the certificate and that there is no way to verify the certificate chain. Hardcoding the fingerprint makes it hard to update the certificate and the lack of verification of the certificate chain seems like a security risk. Are the workarounds for this? Is there a way to use verifyCertChain with ESP8266httpUpdate? Am I missing something obvious?
One thought I had was to load the certificate with client.setCACert_P then verify it, then get it's fingerprint (how?) then use that fingerprint with ESP8266httpUpdate. Is this a good thought? What's a better thought?
The text was updated successfully, but these errors were encountered:
@igrr Is there any option/alternative in the latest git version to pass WiFiClientSecure object to the update method after certificate verification.
I also checked your post https://gist.github.com/igrr/24dd2138e9c8a7daa1b4 .
This looks like it was fixed via #4980 where you can create a BearSSL::WiFiClientSecure with any kind of validation options needed and pass it into ESP8266httpUpdate().
Basic Infos
Hardware
Hardware: ESP-12F
Core Version: github commit 7b09ae5 Nov 22 2017
Description
ESP8266httpUpdate supports https, which is great, but it appears I have to hardcode the fingerprint of the certificate and that there is no way to verify the certificate chain. Hardcoding the fingerprint makes it hard to update the certificate and the lack of verification of the certificate chain seems like a security risk. Are the workarounds for this? Is there a way to use verifyCertChain with ESP8266httpUpdate? Am I missing something obvious?
One thought I had was to load the certificate with client.setCACert_P then verify it, then get it's fingerprint (how?) then use that fingerprint with ESP8266httpUpdate. Is this a good thought? What's a better thought?
The text was updated successfully, but these errors were encountered: