cloudflare-tor/what-to-do.md

16 KiB
Raw Blame History

What you can do to resist Cloudflare?

< Matthew Prince (@eastdakota)

"Id suggest this was armchair analysis by kids its hard to take seriously." (source)


Website consumer
  • If the website you like is using Cloudflare, tell them not to use Cloudflare.
"Ask and it will be given to you; seek and you will find; knock and the door will be opened to you."

If you don't ask for it, website owner never know this problem. Example below. Successful example. Raise your voice.

You are just helping corporate censorship and mass surveillance.
https://trac.torproject.org/projects/tor/ticket/24351
Your web page is in the privacy-abusing private walled-garden of CloudFlare.
See https://github.com/privacytoolsIO/privacytools.io/issues/374#issuecomment-460077544
  • Take some time to read website's privacy policy. It must explain what the "Cloudflare" is, and ask for permission to share your(user) data with CF. Failure to do so will result in the breach of trust and the website in question should be avoided.

An acceptable privacy policy example is here (look at "Subprocessors" > "Entity Name")

I've read your privacy policy and I cannot find the word "Cloudflare".
I refuse to share data with you if you continue to feed my data to Cloudflare.
See https://notabug.org/themusicgod1/cloudflare-tor/src/master/README.md

For example, Liberland Jobs privacy policy says:

... is not going to happen. Cloudflare have their own "privacy policy", and there's no way to hear customer's privacy policy needs. Cloudflare loves doxxing people.

Here's a good example for website's signup form. AFAIK, zero website do this. Will you trust them?

By clicking “Sign up for XYZ”, you agree to our terms of service and privacy statement.
You also agree to share your data with Cloudflare and also agrees to cloudflare's privacy statement.
If Cloudflare leak your information, it's not our fault. [*]

[ Sign up for XYZ ] [ I disagree ]

[*] https://www.wired.com/2017/02/crazy-cloudflare-bug-jeopardized-millions-sites/

  • Try not to use their service. Remember you are being watched by Cloudflare.

  • Search for other website. There are many alternatives and opportunites on the internet!

  • If your browser is Firefox, use one of these add-ons.

Name Developer Support Can Block Can Notify
Block Cloudflare MITM Attack Project BCMA Link Yes Yes
Block Cloudflare MITM Attack nullius Link Yes Yes
Are links vulnerable to MITM? Maslin Bossé Link No Yes
Third-party Request Blocker (AMO) Searxes #Addon Link Yes Yes
TPRB Sw Link Yes Yes
Detect Cloudflare Frank Otto Link No Yes
Cloud Firewall [*] Gokulakrishna Sudharsan Link Yes No

[*] Do not use it if you're using proxy/VPN/Tor because it has "DNS leak".

  • Convince your friends to use Tor Browser on the daily basis. Anonymity should be the standard of the open internet!

Website owner / Web developer

  • Do not use Cloudflare solution. You can do better than that, right?

  • Want more customers? You know what to do. Hint is "above line".

  • Using Cloudflare will increase chances of an outage. Visitors can't access to your website if your server is down or Cloudflare is down. Did you really think Cloudflare never go down? Another sample.

  • Using Cloudflare to proxy your "API service" will harm your customer. A customer called you and said "I can't use your API anymore", and you have no idea what is going on. Cloudflare can silently block your customer. Do you think it is okay?

  • Do you need HTTPS certificate? Use "Let's Encrypt" or just buy it from CA company.

  • Do you need DNS server? Can't set up your own server? Then how about Dyn.com, Hurricane Electric Free DNS or this?

  • Looking for hosting service? "Free" only? Well, how about this?

  • Are you using "cloudflare-ipfs.com"? Do you know Cloudflare IPFS is bad?

  • Install Web Application Firewall (such as OWASP) and Fail2Ban on your server and configure it properly.

  • If you want to know more alternative solutions, take a look at this blog's "Alternative solutions" section.

  • Redirect or block "Cloudflare Warp" users from accessing your website. And provide a reason if you can.

IP list is from "Cloudflares current IP ranges" webpage. They might lie, so check your server logs too.

Method A: Just block

server {
...
deny 173.245.48.0/20;
deny 103.21.244.0/22;
deny 103.22.200.0/22;
deny 103.31.4.0/22;
deny 141.101.64.0/18;
deny 108.162.192.0/18;
deny 190.93.240.0/20;
deny 188.114.96.0/20;
deny 197.234.240.0/22;
deny 198.41.128.0/17;
deny 162.158.0.0/15;
deny 104.16.0.0/12;
deny 172.64.0.0/13;
deny 131.0.72.0/22;
deny 2400:cb00::/32;
deny 2606:4700::/32;
deny 2803:f800::/32;
deny 2405:b500::/32;
deny 2405:8100::/32;
deny 2a06:98c0::/29;
deny 2c0f:f248::/32;
...
}

Method B: Redirect to warning page

http {
...
geo $iscf {
default 0;
173.245.48.0/20 1;
103.21.244.0/22 1;
103.22.200.0/22 1;
103.31.4.0/22 1;
141.101.64.0/18 1;
108.162.192.0/18 1;
190.93.240.0/20 1;
188.114.96.0/20 1;
197.234.240.0/22 1;
198.41.128.0/17 1;
162.158.0.0/15 1;
104.16.0.0/12 1;
172.64.0.0/13 1;
131.0.72.0/22 1;
2400:cb00::/32 1;
2606:4700::/32 1;
2803:f800::/32 1;
2405:b500::/32 1;
2405:8100::/32 1;
2a06:98c0::/29 1;
2c0f:f248::/32 1;
}
...
}

server {
...
if ($iscf) {rewrite ^ https://example.com/cfwsorry.php;}
...
}


[ code cfwsorry.php ]

<?php
header('HTTP/1.1 406 Not Acceptable');
echo <<<CLOUDFLARED
Thank you for visiting ourwebsite.com!
We are sorry, but we can't serve you because your connection is being intercepted by Cloudflare.
Please read https://notabug.org/themusicgod1/cloudflare-tor/ for more information.
CLOUDFLARED;
die();

Software user
  • If you use Debian GNU/Linux, or any derivative, subscribe to bug #831835. And if you can, help verify the patch, and help the maintainer come to the right conclusion on whether it should be accepted.

  • Always recommend Tor Browser for desktop and Tor Browser for Android, Orfox for smartphone. Other software's privacy is imperfect. This doesn't mean Tor browser is "perfect". There is no 100% secure nor 100% private on the internet and technology.

  • Don't want to use "Tor"? You can use Tor Browser without Tor, and this is the best option for you.

How?

  1. Download Tor Browser and launch it.
  2. Open Add-ons Manager (about:addons) and disable EVERYTHING but "Torbutton". Do NOT remove them.
  3. Open about:config and search "extensions.torbutton.use_nontor_proxy". Set it to "true".
  4. Go to Options, scroll down to "Network Proxy". Click "Settings" and select "No proxy".
  5. Close Tor Browser.

Other guide is here.

Let's talk about other software's privacy...

Therefore we recommend "Tor Browser" only. Nothing else.


"Mozilla Firefox" user
  • Don't use Firefox Nightly. It will send debug-level information to Mozilla servers without opt-out method. Mozilla servers are behing Cloudflare.

  • It is possible to prohibit Firefox to connect to Mozilla servers. Create a file "/distribution/policies.json". Mozilla's policy-templates guide. Keep in mind this trick might stop working in later version because Mozilla likes to whitelist themselves. Use firewall and DNS filter to block them completely.

"WebsiteFilter": {
  "Block": [
  "*://*.mozilla.com/*",
  "*://*.mozilla.net/*",
  "*://*.mozilla.org/*",
  "*://*.firefox.com/*",
  "*://*.thunderbird.net/*",
  "*://*.cloudflare.com/*"
  ]
},
  • Report a bug on mozilla's tracker, telling them not to use Cloudflare/TRR. There was a bug report on bugzilla. Many people were posted their concern, however the bug was hidden by the admin last year.

  • To disable DOH, enter about:config?filter=network.trr in the address bar then set "network.trr.mode" to 5 to completely disable it. The value "5" means "Off by choice".

How?

  1. Download Tor and install it on your computer.
  2. Add this line to "torrc" file. DNSPort description. DNSPort 127.0.0.1:53
  3. Restart Tor.
  4. Set your computer's DNS server to "127.0.0.1".
  • Tell us if you see this functionality start to creep up beyond Firefox Nightly into more stable versions of Firefox.

Action
  • Tell others around you about the dangers of Cloudflare. But don't talk with NSA employee; you'll be definitely marked... just kidding!

  • Help improve this repository, both the lists, the arguments against it and the details.

  • Document and make very public where things go wrong with Cloudflare (and similar companies), making sure to mention this repository when you do so ;)

  • Get more people using Tor by default so they can experience the web from the perspective of different parts of the world.

  • Start groups, in social media and meatspace, dedicated to liberating the world from Cloudflare.

  • Where appropriate, link to these groups on this repository - this can be a place for coordinating working together as groups.

  • Start a coop that can provide a meaningful non corporate alternative to Cloudflare.

  • Let us know of any alternatives to help at least provide multiple layered defence against Cloudflare.

  • If you are a Cloudflare customer, set your privacy settings, and wait for them to violate them. Then bring them under anti-spam / privacy violation charges.

  • Try using globalist to maintain this list.

  • If you are in the United States of America and the website in question is a bank or an accountant, try to bring legal pressure under the GrammLeachBliley Act, or the Americans with DIsabilities Act and report back to us how far you get.

  • If the website is a government site, try to bring legal pressure under the 1st Amendment of the US Constitution.

  • If you are EU citizen, contact the website to send your personal information under the General Data Protection Regulation. If they refuse to give you your information, that's a violation of the law.

  • For companies that claim to offer service on their website try reporting them as "false advertising" to consumer protection organizations and BBB. Cloudflare websites are served by Cloudflare servers.

  • The ITU suggest in the US context that Cloudflare is starting to get big enough that antitrust law might be brought down upon them.

  • It's conceivable that the GNU GPL v4 could include a provision against storing source code behind such a service, requiring for all GPLv4 and later programs that at least the source code is accessible via a medium that does not discriminate against tor users (or any other class of users or something?)


Now, what did you do today?