Tried it out from the console using Chromium on Linux. It's a segfault of some form, though it unfortunately doesn't log anything else to the terminal before segfaulting.
Maybe put a warning (something in the title) which tells that opening the page may cause our browser to crash? I thought it would open a page where the issue is discussed, not a page which directly crashes my browser. (HN hides the subdomain: demo.cmrg.net, therefore removing the only indicator showing that this is a demo)
That's quite annoying. It doesn't indicate that clicking this link kills Chrome rather than a disclosure piece about something that could kill Chrome. I'd be even more annoyed if this crashed and lost unsaved work.
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.
Does 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."
16 comments
[ 9.0 ms ] story [ 62.1 ms ] threadAnyone know what's going on here?
Yes, killed Chrome 33.0.1750.146 m on Win7 here.
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.
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."