From 24d78c8f76d091b44edc773e8465ea31431d0c20 Mon Sep 17 00:00:00 2001
From: Zhiming Wang <zmwangx@gmail.com>
Date: Thu, 1 Sep 2016 22:16:29 +0800
Subject: Latest post: Minor update on whitelisting Tor traffic

---
 source/blog/2016-09-01-this-blog-is-now-behind-cloudflare.md | 2 ++
 1 file changed, 2 insertions(+)

(limited to 'source/blog')

diff --git a/source/blog/2016-09-01-this-blog-is-now-behind-cloudflare.md b/source/blog/2016-09-01-this-blog-is-now-behind-cloudflare.md
index e471ec8e..8bfde9b3 100644
--- a/source/blog/2016-09-01-this-blog-is-now-behind-cloudflare.md
+++ b/source/blog/2016-09-01-this-blog-is-now-behind-cloudflare.md
@@ -15,3 +15,5 @@ After careful evaluation, I decided that CloudFlare's SSL model is good enough f
 End result: this blog is now behind CloudFlare. Readers should now see that green HTTPS badge again (note that I'm enforcing HTTPS — without HSTS though). As for CAPTCHAs, I have adjusted the firewall settings on CloudFlare's dashboard — "Security Level" to "Essentially Off" and "Challenge Passage" to 1 year, so hopefully it won't be too annoying.[^tor]
 
 [^tor]: I don't use Tor, and don't intend to raise Big Brother's suspicion by using it, so I have no idea of the actual Tor experience.
+
+**09/01/2016 Update.** I just realized that [CloudFlare supports whitelisting Tor traffic](https://support.cloudflare.com/hc/en-us/articles/203306930-Does-CloudFlare-block-Tor-). Did that.
-- 
cgit v1.2.1