summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBen Burwell <ben@benburwell.com>2016-04-08 18:02:14 -0400
committerBen Burwell <ben@benburwell.com>2016-04-08 18:02:14 -0400
commit8fef58a703ec0aa06a856d6cf78c061379e61b32 (patch)
tree568aab3f0630a0cdee48f81eaf09be3e44f56cdc
parent5db48c8413f3211c9514e69483ff840e552d6e14 (diff)
Add Whitelisting Tor on Cloudflare post
-rw-r--r--_posts/2016-04-08-whitelisting-tor-on-cloudflare.markdown53
-rw-r--r--assets/images/tor.pngbin0 -> 34700 bytes
2 files changed, 53 insertions, 0 deletions
diff --git a/_posts/2016-04-08-whitelisting-tor-on-cloudflare.markdown b/_posts/2016-04-08-whitelisting-tor-on-cloudflare.markdown
new file mode 100644
index 0000000..365eea7
--- /dev/null
+++ b/_posts/2016-04-08-whitelisting-tor-on-cloudflare.markdown
@@ -0,0 +1,53 @@
+---
+title: Whitelisting Tor on CloudFlare
+description: >
+ CloudFlare poses an insignificant barrier to Tor users, but site operators can
+ ease their way by whitelisting Tor.
+layout: post
+date: 2016-04-08 00:00:00
+image: https://www.benburwell.com/assets/images/tor.png
+---
+
+On March 30th, 2016, CloudFlare posted [a blog entry entitled "The Trouble with
+Tor"](https://blog.cloudflare.com/the-trouble-with-tor/) outlining the issues
+Cloudflare has with serving clients' sites to Tor users. The Tor project quickly
+followed it up with [their own post, "The Trouble with
+CloudFlare"](https://blog.torproject.org/blog/trouble-cloudflare), which
+presented an analysis of the situation from Tor's perspective.
+
+<!--more-->
+
+CloudFlare's post acknowledged that Tor does play an important role on the
+internet, but presents the irrelevant conclusion that of "Security, Anonymity,
+Convenience: Pick Any Two," security and convenience will necessarily be the
+choices of their customers. Certainly, all three properties are important, but
+not all of their customers' sites will be subject to the same risks.
+
+I use CloudFlare's services on several sites, including this one. On some of my
+sites, I do rely on CloudFlare to provide some measure of security, particularly
+ones with dynamic content. However, for a site like this one that is entirely
+static, I have nothing to gain from hiding my content due to a perceived
+security threat. Everything on this site is considered public, and there are no
+attack vectors that are prevented through CloudFlare doing browser verification.
+
+On the other hand, anonymity is quite important to me. Where it does not present
+a security risk to disable CloudFlare's browser verification, I have chosen to
+whitelist Tor users on this site. There is little to be lost from bots or
+spammers accessing this site at will, and there is much to be gained from
+ensuring that people who consider their privacy important to be able to access
+content without undue hinderance.
+
+CloudFlare does provide an easy way to whitelist all Tor traffic, and they even
+presented it in their original blog post. To whitelist Tor, go to the Firewall
+app in your CloudFlare dashboard and add an Access Rule. Enter `T1` as the
+country code (the special code for Tor), and select Whitelist as the action.
+Now, Tor users will not be presented with a CAPTCHA when visiting your site.
+
+To see it in action for yourself, [download the Tor
+browser](https://www.torproject.org/projects/torbrowser.html.en) and try
+visiting your site before and after adding the firewall rule. More information
+about how CloudFlare handles Tor traffic can be found [on their Help Center
+page](https://support.cloudflare.com/hc/en-us/articles/203306930-Does-CloudFlare-block-Tor-).
+
+While whitelisting Tor is not the right solution for every site, I encourage you
+to consider whether yours is a good candidate. Let me know your thoughts!
diff --git a/assets/images/tor.png b/assets/images/tor.png
new file mode 100644
index 0000000..3bbe6d6
--- /dev/null
+++ b/assets/images/tor.png
Binary files differ