Recent comments on posts in the blog:
Well written, thanks.
However, you may find useful my blog post about prefetching resources, see: http://zinoui.com/blog/prefetching-resources
Why encrypt DNS when your browser still leaks the domain name via SNI extension, even though it runs over https? https://wikipedia.org/wiki/Server_Name_Indication
There's some documentation on https://wiki.debian.org/HowTo/dnsmasq
Unfortunately this setup still leaks the client IP address to the resolver. There's no way to use dnscrypt over Tor yet: https://github.com/jedisct1/dnscrypt-proxy/issues/234
Not sure if dnscrypt-proxy caches but it doesn't seem that useful as general advise if it doesn't and everyone uses a proxy in Iceland.
I don't believe that
dnsproxy-crypt caches (the name implies it doesn't), but Unbound does.
FWIW, my usual solution to captive portals is to add some exceptions to the DNS resolution/HTTP proxy, which forces enough requests to go "directly" to be able to log into the captive portal. Eg, the domain of the place I'm staying in, and the domain of whatever Wifi provider they're using. Then I trigger the captive port by, eg, trying to go to the domain of the place I'm staying in. Over time one could accumulate a list of such exceptions required (and it seems like something that could be crowd sourced).
For better privacy one would perhaps want to selectively enable these exceptions based on the current location (and/or selectively disable them if at known locations like home/work/etc when it's not needed).
PS: If your names are resolved from a location far away from you, you'll also generally get CDN nodes which are far away from you. Which may lead to poor performance. YMMV.
Do "network.cookie.lifetimePolicy" and "network.cookie.lifetime.days" affect exception domains that I explicitly set to allow cookies?
Following this STACKOVERFLOW's question, if the dump format is text
$ sed -n -e '/COPY.*mytable/,/CREATE TABLE/p' pg_whole.dump > mytable.dump
This might be common sense but...
-> pwd /home/foo
-> git log -- bar
This will return nothing
-> git log -- baz/bar
This will return the history of the file bar in the directory baz