CloudFlare's Heartbleed challenge cracked

Re:CloudFlare's Heartbleed challenge cracked by alex_marchant on Friday April 11, 2014 @09:24PM (#7576515)

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.

[ Parent | on HN ]

Re:CloudFlare's Heartbleed challenge cracked by nolok on Friday April 11, 2014 @09:29PM (#7576539)

Subdomains are separate domains, and you put www.cloudflarechallenge.com in your hosts, so when going to the domain without the www subdomain your entry in the hosts is not used.

Either go to https://www.cloudflarechallenge.com or remove the www subdomain from your hosts entry.

[ Parent | on HN ]

Re:CloudFlare's Heartbleed challenge cracked by gojomo on Friday April 11, 2014 @09:29PM (#7576540)

Try setting 'www.cloudflarechallenge.com' in /etc/hosts instead, and when visiting the URL hit <shift>-<reload> to ensure your browser isn't caching anything.

I see Indutny's blog for 'https://www.cloudflarechallenge.com'[/etc/hosts mapped to 165.225.128.15] in both FF and Chrome.

[ Parent | on HN ]

Re:CloudFlare's Heartbleed challenge cracked by alex_marchant on Friday April 11, 2014 @09:46PM (#7576603)

Ok adding www to the hosts entry worked, appreciate it

[ Parent | on HN ]

Re:CloudFlare's Heartbleed challenge cracked by quasque on Friday April 11, 2014 @10:40PM (#7576754)

Also possible to verify using OpenSSL commandline:

    openssl s_client -connect 165.225.128.15:443 -showcerts \ 
                  -servername www.cloudflarechallenge.com

(Though to fully check, you need to compare certificates with the one off the real site, and ensure that his blog appears upon an HTTP request - to exclude proxying.)

[ Parent | on HN ]

Re:CloudFlare's Heartbleed challenge cracked by fletchowns on Friday April 11, 2014 @09:29PM (#7576536)

Try https://www.cloudflarechallenge.com/

[ Parent | on HN ]