Palum
what Suineg set it to
sites-using-cloudflare/README.md at master · pirate/sites-using-cloudflare · GitHub
So basically a ton of sites it looks like?
So basically a ton of sites it looks like?
- 1
That is what happened to rerolled.sites-using-cloudflare/README.md at master · pirate/sites-using-cloudflare · GitHub
So basically a ton of sites it looks like?
It definitely was archived by search engines. 2.5 million sites for more than a year. Lololol
This is one reason I haven't pulled the trigger on using them yet. I don't want them in the middle.Cloud flare is downplaying, but Google is saying assume the worst. That's good advice anyway.
Bitcoin sites and Patreon being affected seem to be the most interesting sites on the list since they deal with money.What should I do?
Check your password managers and change all your passwords, especially those on these affected sites. Rotate API keys & secrets, and confirm you have 2-FA set up for important accounts. This might sound like fear-mongering, but the scope of this leak is truly massive, and due to the fact that all cloudflare proxy customers were vulnerable to having data leaked, it's better to be safe than sorry.
Theoretically sites not in this list can also be affected (because an affected site could have made an API request to a non-affected one), you should probably change all your important passwords.
Submit PR's to add domains that you know are using cloudflare, or remove domains that are not affected.
No, Project Zero said it was not related. However, something else did happen that Google hasn't disclosed yet.is this why Gmail asked me to re-enter my password yesterday?
Might be related to the SHA1 collision proof that google did this week?No, Project Zero said it was not related. However, something else did happen that Google hasn't disclosed yet.
Best theory I saw was that Google was still using SHA1 somewhere in their authentication chain. But that's just rumors, so far Google has acknowledged it, said there is nothing to be concerned about, and nothing else.Might be related to the SHA1 collision proof that google did this week?