4 ms·

If your site is protected by CloudFlare (like HN is), you are automatically protected from this vulnerability (see: http://blog.cloudflare.com/staying-ahead-of-

• amalcon 13y ago
  This is perhaps somewhat misleading. It's possible that this bug was being actively exploited before now, so you should change your keys even if you use a CDN (all the majors have already fixed this as far as I'm aware).
• smtddr 13y ago
  Perhaps Cloudfare should note that the "up to 64kB" isn't entirely correct. http://heartbleed.com/ http://heartbleed.com/ >>There is no total of 64 kilobytes limitation to the attack, that limit applies only to a single heartbeat. Attacker can either keep reconnecting or during an active TLS connection keep requesting arbitrary number of 64 kilobyte chunks of memory content until enough secrets are revealed.
• ars 13y ago
  You are protected now. But you were not before, so if any attacker figured this out before the public disclosure then you have [possibly] already been attacked and compromised.
  • extrapolate 13y ago
    Not entirely correct, as the blog post states: > We fixed this vulnerability last week before it was made public. Although there's still the other 103 weeks this was vulnerable to worry about.