-
Notifications
You must be signed in to change notification settings - Fork 57
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
Indicate SNI support #8
Comments
We'll wait on this one but I do think it'll be important in the relatively near future. How's My SSL is causing churn in a couple of communities, and I'd rather not cause more different kinds of churn in the near term. Also, one of the benefits of howsmyssl is that it has a fairly small set of criteria to match right now. Once some of the churn slows down, we'll come back to this and evaluate in the fullness it deserves. |
If you think that's bogus, hit up the email list. I'm trying to get discussions going there. |
Makes sense, thanks. |
Any chance that this could be looked at again? I could even see this being more generic and just to display all the extensions that the client is providing. They wouldnt need to affect the TLS rating, but would be primarily informative. Its been several years since this issue( and others ) was created and put on hold due to "churn". the only other way I could think of to check for SNI support would be to get a TCPIP capture and inspect the TLS handshake; however this is not always feasible. |
Not strictly security, but it's critical for scaling / deployment.
The text was updated successfully, but these errors were encountered: