-
Notifications
You must be signed in to change notification settings - Fork 322
What specific features were affected? #127
Comments
Anything that routes through Cloudflare could have possibly leaked data via third partys that caused the leak to occur. |
Id love to see proof of this because nothing I have found officially states this. |
Here's the official blog post, the quote can be found near the end of the post. |
Ive already read that one, doesn't prove anything |
The whole blog post goes into detail explaining why, and what exactly happened. It's been published by Cloudflare themselves. Personally i'd say this is proof enough, especially if potentially confidential data was leaked. |
Now show me proof that every site listed in this repo was affected. |
The key words are Every website routed through Cloudflare's CDN solutions had a slim chance of leaking data via other, unrelated websites where the bug occured - as long as it happened on the same proxy node. |
Even sites cloudflare has manually emailed saying they're not affected are not "proven" to be unaffected: #87 (comment) |
If I use FULL ssl encryption from end to end is it possible that my websites 'were' affected? I have read in many places that it is only the Flexible SSL that was affected, is this true?
The text was updated successfully, but these errors were encountered: