CloudFlare's Heartbleed challenge cracked
11–20 of 155 posts
Re: CloudFlare's Heartbleed challenge cracked
#12https://twitter.com/indutny/status/454767565991325697 How do you not love this guy.
Re: CloudFlare's Heartbleed challenge cracked
#13Re: CloudFlare's Heartbleed challenge cracked
#14https://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.
Just awesome. Only 3 hours to rip out the key!
Re: CloudFlare's Heartbleed challenge cracked
#15Re: CloudFlare's Heartbleed challenge cracked
#16So 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.
Anything you'd send to a web server or receive from a web server is presumed compromised.
Re: CloudFlare's Heartbleed challenge cracked
#17https://twitter.com/indutny/status/454767565991325697 How do you not love this guy.
Re: CloudFlare's Heartbleed challenge cracked
#18https://twitter.com/indutny/status/454767565991325697 How do you not love this guy.
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
#19https://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.
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
#20Earlier 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.