3 ms·
Cloudflare's announcement, as it is currently worded, deserves the understatement-of-the-centry award.
by dmitrygr 10y ago
Cloudflare's announcement, as it is currently worded, deserves the understatement-of-the-centry award.
- jlgaddis 10y agoYep, even Tavis said it "severely downplays the risk".
- masterleep 10y agoIs that because, even though a very small number of pages (they claim) triggered the bug, any adjacent traffic in memory could be disclosed? That traffic could be basically anything sent through Cloudflare, it would seem.
- deleted 10y ago[deleted]
- deleted 10y ago[deleted]
- danielweber 10y ago"Don't worry, the keys weren't compromised." I know how to replace my TLS keys. I have no idea how to replace everything else. It's like people who think losing my credit card number is the worst thing. No, it can be a hassle, but once I replace it I'm okay. It's everything else.
- fulafel 10y agoThe implied comparison to Heartbleed problem is that everyone's old encrypted traffic was suddenly in the open, key change didn't help. (except for the enlightened few who used PFS before Heartbleed)
- sneak 10y agoOnly three thousand something sites [were potentially serving private data from all 7 million customer domains we host]
- creshal 10y agoIf the bug exposes random uninitialized memory, can't it affect a lot more sites? And if it truly is only ~3000 sites, where's the list?