aboutsummaryrefslogtreecommitdiff
path: root/source/blog
diff options
context:
space:
mode:
authorZhiming Wang <zmwangx@gmail.com>2016-09-01 22:16:29 +0800
committerZhiming Wang <zmwangx@gmail.com>2016-09-01 22:16:29 +0800
commit24d78c8f76d091b44edc773e8465ea31431d0c20 (patch)
tree8d915fb4a57f4cac94dfc8e8e08941f4e3b5b96f /source/blog
parentab39a77b0eb4ce3e8fa219ea76fb9616a8aa7758 (diff)
downloadmy_new_personal_website-24d78c8f76d091b44edc773e8465ea31431d0c20.tar.xz
my_new_personal_website-24d78c8f76d091b44edc773e8465ea31431d0c20.zip
Latest post: Minor update on whitelisting Tor traffic
Diffstat (limited to '')
-rw-r--r--source/blog/2016-09-01-this-blog-is-now-behind-cloudflare.md2
1 files changed, 2 insertions, 0 deletions
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.