Live data from Hacker News

CloudFlare's Heartbleed challenge cracked

twitter.com

11–20 of 155 posts

Re: CloudFlare's Heartbleed challenge cracked

#14
post #7
post #3

https://twitter.com/indutny/status/454767565991325697 How do you not love this guy.

Core node.js dev, based in Moscow, commits open source almost daily, works at Voxer, cracks security for fun. I love the internet.

https://twitter.com/indutny/status/454783660886360064

Just awesome. Only 3 hours to rip out the key!

Re: CloudFlare's Heartbleed challenge cracked

#16

So this does mean that I need to change my passwords on every damn site on the list? Oh bollocks, those passwords were a work of art.

No. This means you need to change keys for every ssl service you run. Passwords were known to be leaked earlier.

Really it means (as everyone assumed in the first place) that anything a web server might have in its heap needs to be totally thrown away. Private keys. Passwords. Credit card numbers. Security questions/answers. Sessions.

Anything you'd send to a web server or receive from a web server is presumed compromised.

Re: CloudFlare's Heartbleed challenge cracked

#18
post #3

https://twitter.com/indutny/status/454767565991325697 How do you not love this guy.

Can someone elaborate on what's going on here?

If i replace his IP with some other random IP I get a 400 bad request error, so it's obvious that it works, but curious how that resolves.

Re: CloudFlare's Heartbleed challenge cracked

#19
post #3

https://twitter.com/indutny/status/454767565991325697 How do you not love this guy.

Can someone elaborate on what's going on here? If i replace his IP with some other random IP I get a 400 bad request error, so it's obvious that it works, but curious how that resolves.

Putting that mapping in /etc/hosts lets your machine skip DNS lookup for that hostname, and just use his IP for that domain name.

Then, your browser checks the received certificate against the authenticated TLS connection, and sees that all is well, allowing you to connect without a warning.

Since the browser does not warn of a certificate mismatch, he must have a valid certificate for 'cloudflarechallenge.com'. QED.

Re: CloudFlare's Heartbleed challenge cracked

#20
post #19

Earlier quoted context omitted.

Can someone elaborate on what's going on here? If i replace his IP with some other random IP I get a 400 bad request error, so it's obvious that it works, but curious how that resolves.

Putting that mapping in /etc/hosts lets your machine skip DNS lookup for that hostname, and just use his IP for that domain name. Then, your browser checks the received certificate against the authenticated TLS connection, and sees that all is well, allowing you to connect without a warning. Since the browser does not warn of a certificate mismatch, he must have a valid certificate for 'cloudflarechallenge.com'. QED.

But seems like only the http connection is working, i get a warning in Chrome when visiting https://cloudflarechallenge.com. Isn't that the only situation where the key would be checked. That's the part that doesn't make sense.
Post reply on HN