-
Notifications
You must be signed in to change notification settings - Fork 13.3k
HTTPS request fails if no fingerprint is provided #2197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi, I understand that it was a Bug, but it was working fine. What I need is an SSL connection without verifying the certificate, isn't that posible? Thanks! |
A SSL connection without verifying the certificate (in any way) just doesn't make much sense. Anyone could easily play "man in the middle" and you'll never notice it. So it's not much better than plain HTTP. |
I need to connect to an API on a server that I don't control. That server requires all connections to go by SSL, so I'm forced to make an SSL connection. I don't control the server, so I can't use the server fingerprint here since the server can change the SSL cert at anytime. My only option is to create an SSL connection without verifying the certificate, I know it's insecure but at the moment I don't see any other solution. I checked and its a common practice between networking libraries that the allow you to decide if you want to verify the certificate or not. What can I do? Thank you very much guys! |
Okay, I got your point. Since I use my own servers, that's not a problem for me. (Locate the sources: Open Arduino IDE -> Preferences, enable the verbose output during compiling; There will be a lot of output if you compile now, but there should be the path of the sources in it. For me (on Linux), it's |
Basic Infos
Hardware
Hardware: Wemos D1 Mini ESP-8266
Core Version: 2.3
Description
http.begin("https://www.google.com")
HTTPS request fails if no fingerprint is provided. On version 2.1 I was able to do the request without providing a fingerprint, can we go back to that?
Thanks!
The text was updated successfully, but these errors were encountered: