6 ms·
DNSCrypt encrypts communications between a DNS client and a DNS resolver
- the8472 7y agoIf you are on a trusted network or have a VPN into a trusted network this is not an issue, you can run your own recursive resolver. The real issue is the traffic between your resolver and the authoritative servers. Using someone else's resolver (secure transport or not) just changes who you're leaking the information to, not the fact that you're leaking.
- tyingq 7y agoWouldn't you be much less personally identifiable one hop upstream?
- tptacek 7y agoThis sounds profound but isn't really saying much, is it? At some point, most Internet protocol privacy issues boil down to who you're willing to leak information to (which is to say, who you choose to trust). And, in the DoH/DNSCrypt case, almost nobody trusts their ISP, so these protocols are valuable.
- vinniejames 7y agoISPs can still see the IP your requests resolves to, and in many cases can still track this info. Unless the site is using shared IP, like many behind caching services, etc
- mantap 7y agoTo your caveat, I can access thepiratebay even though it is supposedly IP blocked in the UK because the courts are not willing to order a block of the whole cloudflare IP range. With so many websites using cloud hosting, it has become very hard for the authorities to block IP ranges. DNS is really the last bastion of government interference. The UK is supposed to be rolling out a nation-wide porn block at some point but it will be totally defeated by encrypted DNS.
- deleted 7y ago[deleted]
- deleted 7y ago[deleted]
- throwawaydoh 7y agoMy Indian ISP blocks certain sites. I use Firefox and has DNS over HTTPS with CloudFlare enabled. I also use CloudFlare's 1.1.1.1 DNS in my router. The sites are still blocked. Firefox shows the error "Secure Connection Failed. An error occurred during a connection to 'site url'. PR_CONNECT_RESET_ERROR". When I search for this error, one of the first results say "this behavior is fairly typical for DPI firewalls". To anyone knowledgeable about this: How can I confirm if my ISP is using DPI?
- StreamBright 7y agohttps://security.stackexchange.com/questions/108985/is-it-possible-to-detect-dpi-deep-packet-inspection https://security.stackexchange.com/questions/108985/is-it-po...
- tgragnato 7y agoFind an (allegedly) blocked website that is using CloudFlare and has TLS 1.3 enabled. In about:config set network.trr.mode=3, network.security.esni.enabled=true, security.OCSP.enabled=0, security.tls.version.max=4, security.tls.version.min=4. Exit, open Firefox again; if the website loads, then your ISP is using a DPI middlebox.
- throwawaydoh 7y agoThank you. Unfortunately, I wasn't able to find a blocked site that has TLS 1.3 enabled. I checked 3 blocked sites after enabling the options you suggested. They were still blocked. I confirmed all 3 didn't have TLS 1.3 by testing them with ssllabs ssltest. All had results show TLS 1.3 as "No".
- 7y ago
- the8472 7y agoFundamentally you have 3 problems 1. securing client - recursive resolver traffic 2. trusting the recursive resolver 3. securing recursive-authoritative traffic. 1. and 2. can both be solved by running your own resolver, either locally, on your gateway or on a VPS reachable via VPN. But doing so makes you more vulnerable to 3. since fewer devices will be pooled behind a single resolver. Thus fixing 3 gives fundamentally a better improvement than futzing around with 1 or 2 where you're still at the mercy of a 3rd party. If you're serious about privacy then DoH/DNSCrypt-via-quad9/cloudflare/etc. just seem like a distraction. I mean sure, encrypting that traffic by default is not bad, but it's not a fundamental improvement. Also, I wouldn't say I trust my ISP, but at least it is under a GDPR jurisdiction. All the big resolvers that advertise encryption are under US jurisdiction, which makes any privacy promises seem hollow.
- xg15 7y ago> At some point, most Internet protocol privacy issues boil down to who you're willing to leak information to (which is to say, who you choose to trust). Except in practice, you as an end-user seldomly have enough information or knowledge to determine if you should trust an entity or not - in fact, is often already expert knowledge to know how many entities are involved. Which is why practically, this question is decided by who has the most power - such as Mozilla in this case deciding all their users should trust Cloudflare. You're absolutely right, in the end, trust is what everything boils down to. I'd consider this an open issue and one of the root causes of many of the internet's problems.
- zzzcpan 7y ago> At some point, most Internet protocol privacy issues boil down to who you're willing to leak information to They don't. As you can leak all your information to a single party or leak smallest necessary bits of information to each of many independent parties to the point where no single party can make any use of it or even decode it alone. Naturally for DNS encrypting communications to authoritative servers can actually improve privacy, while encrypting communications to a big centralized third party resolver and using it only has a negative effect on privacy.
- troquerre 7y agoDNS traffic is often resolved through ISPs even if you use a VPN. https://security.stackexchange.com/questions/13900/if-i-use-a-vpn-who-will-resolve-my-dns-requests https://security.stackexchange.com/questions/13900/if-i-use-...
- the8472 7y agoThat's configurable and depends on your VPN use. If you just want to reach some internal corporate network ranges and have everything else go directly to the internet that's perfectly fine. If you're using a VPN for privacy reasons you have to set it up properly of course. On linux network namespaces can help with that where you can make sure that default namespace goes through your VPN and your ethernet device gets moved to a separate namespace that applications don't even see by default.
- chewz 7y agoDNSCrypt-proxy allows to send queries to random upstream DNS server or to better half of them. Spreading your queries along many servers makes them difficult to analyze. [1] https://github.com/DNSCrypt/dnscrypt-proxy/blob/master/dnscrypt-proxy/example-dnscrypt-proxy.toml https://github.com/DNSCrypt/dnscrypt-proxy/blob/master/dnscr...
- toortam 7y agoStubby is another alternative, it uses DoT (DNS over TLS).
- stephen_g 7y agoYeah, I really like Stubby. Just last week I set up a Raspberry Pi with Stubby and Unbound, it was actually pretty easy. Stubby is doing DoT and DNSSEC validation, and Unbound handling caching and a local zone for my home devices, which is really nice. I might look at trying Pi-hole eventually instead of Unbound to do DNS level ad/tracker blocking but I'll keep Stubby there to do the DoT.
- 8K832d7tNmiQ 7y agoGood thing someone make a user-friendly version of it on Windows https://www.microsoft.com/store/apps/9PM3VVLB6NDQ https://www.microsoft.com/store/apps/9PM3VVLB6NDQ
- w8rbt 7y agoI use CoreDNS as a stub resolver to do DNS over TLS. It works great. https://coredns.io/ https://coredns.io/
- 3xblah 7y agoCurveDNS encrypts communications between a DNS resolver and an DNS authoritative server. https://curvedns.on2it.net https://curvedns.on2it.net
- iam-TJ 7y agoFirefox doesn't like the certificate there, which is rather ironic: Web sites prove their identity via certificates. Firefox does not trust this site because it uses a certificate that is not valid for curvedns.on2it.net. The certificate is only valid for the following names: www.github.com, .github.io, .githubusercontent.com, *.github.com, github.com, github.io, githubusercontent.com Error code: SSL_ERROR_BAD_CERT_DOMAIN
- jfindley 7y agoI think the project has moved to https://dnscurve.io/ https://dnscurve.io/ - I can't say for certain this is the same project but it's the current website for github.com/curvedns/curvedns which I believe is the software behind GP's link.
- iosonofuturista 7y agoSeems to be a even more terrible than usual naming decision. It appears that DNSCurve is the protocol, and CurveDNS is an implementation. And the official page for the protocol seems to reside at http://www.dnscurve.org http://www.dnscurve.org. What a mess.
- donmcronald 7y agoIt's https://curvedns.github.io/curvedns https://curvedns.github.io/curvedns hosted on GitHub Pages giving a (301) redirect. How did they get a header based redirect via GitHub pages?
- Arnavion 7y agohttps://github.com/curvedns/curvedns/blob/gh-pages/CNAME https://github.com/curvedns/curvedns/blob/gh-pages/CNAME https://duckduckgo.com/?q=github+pages+"cname+file" https://duckduckgo.com/?q=github+pages+"cname+file" The official GH docs at https://help.github.com/en/articles/using-a-custom-domain-with-github-pages https://help.github.com/en/articles/using-a-custom-domain-wi... don't seem to talk about it (any more?) as opposed to the web UI way of setting the custom domain. There is a small mention at https://help.github.com/en/articles/troubleshooting-custom-domains#github-repository-setup-errors https://help.github.com/en/articles/troubleshooting-custom-d...
- jakeogh 7y agohttps://github.com/DNSCrypt/dnscrypt-proxy https://github.com/DNSCrypt/dnscrypt-proxy works well
- exabrial 7y agoAnd the best part is it's still based on UDP
- bluejekyll 7y agoAs DNS-over-Quic starts shaping up, this probably won’t matter, in terms of latency.
- techntoke 7y agoSo this whole Firefox DoH is a moot point when these other options exist. Why Mozilla must you insist on making this more difficult?
- tiew9Vii 7y agoApplications should respect OS settings unless told otherwise by a user i.e opt in not opt out. It’s useful Firefox has the option to enable dns over https for users who do not run their own dns, dnscrypt, stubby servers etc but it should absolutely be opt in otherwise it’s bypassing any custom dns servers setup already. I run a small OpenBSD router with stubby for dns over tls and unbound for caching. Unbound is also loaded with a dns blocklist for adblocking/malicious site blocking which unfortunately would get bypassed automatically by browser defaults. OpenBSD just patched Firefox to disable doh by default.
- techntoke 7y agoThere probably already exists, but I would like to see a standardized Docker setup for encrypted DNS and running your own DNS with unbound. I run both Unbound and Nsd locally, but I probably have a lot I could improve upon. I just used what few informative tutorials I was able to find.
- dngray 7y agoThe arch wiki actually has a section on using unbound, dnsmasq, pdnsd with dnscrypt: https://wiki.archlinux.org/index.php/Dnscrypt-proxy#Local_DNS_cache_configuration https://wiki.archlinux.org/index.php/Dnscrypt-proxy#Local_DN... I do this on my router, and then force all of it over the VPN with a socks proxy.
- techntoke 7y agoAny chance you could setup that in a Docker contaienr?
- 7y ago
- eganist 7y agoGood reddit thread discussing the differences between the following (I googled it specifically to find out what practical differences existed between DNS over TLS and DNSCrypt): * DNS over HTTPS (DoH) * DNS over TLS (DoT) * DNSCrypt https://www.reddit.com/r/privacy/comments/89pr15/dnsoverhttps_vs_dns_overtls_vs_dnscrypt/ https://www.reddit.com/r/privacy/comments/89pr15/dnsoverhttp... TL;DR: It looks like DoT probably achieves much the same thing but may have more support through standardized implementations at least compared to DNSCrypt. I disregarded the top comment's opinion about DoH since their position is likely influenced by their state of competition with Cloudflare.
- yegle 7y agoMost of the top comments in the thread are 1 years old now. DoH back then I think only have a Google DNS flavor which send request as human readable POST data or query string and respond in JSON. Since then the DoH has been standardized under RFC 8484 (not final yet) and switched to use DNS wire format. DoT may have wider support right now due to 1) Android P have built-in support, and 2) Debian 10 uses subby as local DNS cache which send upstream request over DoT. But I think DoH is catching up since Firefox and now Chrome are going to support it. I would assume Apple and Microsoft would follow along and add the DoH support to their browsers.
- dngray 7y ago> But I think DoH is catching up since Firefox and now Chrome are going to support it. I would assume Apple and Microsoft would follow along and add the DoH support to their browsers. I think DoHs will end up being the standard that 'wins' as such because DoT can be banned by governments who do not want you doing it. In addition to that I can see at some point DoHs becoming DNS over QUIC. It seems as if QUIC is now a part of HTTP/3 so that's quite likely. When the standards finalize: • https://datatracker.ietf.org/doc/draft-ietf-quic-transport/ https://datatracker.ietf.org/doc/draft-ietf-quic-transport/ • https://datatracker.ietf.org/doc/draft-huitema-quic-dnsoquic/ https://datatracker.ietf.org/doc/draft-huitema-quic-dnsoquic... What is interesting is DNSCrypt https://dnscrypt.info/faq https://dnscrypt.info/faq also acknowledge that fact under the section for DoHS: "Will automatically benefit from improvements made to HTTP/2 and, eventually, QUIC"
- godzillabrennus 7y agoI’m going to give Pi-Hole a try at home. Seems like there are guides for dns crypt to be enabled with it. Wish it was bundled with the official build though.