TLS handshake that kills Chrome
11–17 of 17 posts
Killed Google Chrome release 35.0.1862.2 Ubuntu unstable package too
Re: TLS handshake that kills Chrome
#12The corresponding bug report: https://code.google.com/p/chromium/issues/detail?id=348987
Re: TLS handshake that kills Chrome
#13That is very irresponsible.
Don't submit a direct link that crashes the whole browsers instead post a communication explaining the risks (also stop upvoting this!). It is also irresponsible since Google has a well publicized framework that enables responsible disclosure that this should have gone through first.
Re: TLS handshake that kills Chrome
#14Wouldn't this potentially be eligible for an security award, and disclosing it this way negates that award?
Re: TLS handshake that kills Chrome
#15Does not kill Chrome Version 27.0.1453.110 on Redhat 6.4
Instead says:
"Server has a weak ephemeral Diffie-Hellman public key This error can occur when connecting to a secure (HTTPS) server. It means that the server is trying to set up a secure connection but, due to a disastrous misconfiguration, the connection wouldn't be secure at all!
In this case the server needs to be fixed. Google Chrome won't use insecure connections in order to protect your privacy."
Re: TLS handshake that kills Chrome
#16Did not kill chromium based epic browser.
Re: TLS handshake that kills Chrome
#17[deleted]