13 ms·
DNS over HTTPS
- therealmarv 9y agodingo - a Google DNS-over-HTTPS caching proxy in Go https://news.ycombinator.com/item?id=12514170 https://news.ycombinator.com/item?id=12514170
- sairamkunala 9y agosimilar - stubby - https://dnsprivacy.org/wiki/display/DP/DNS+Privacy+Daemon+-+Stubby https://dnsprivacy.org/wiki/display/DP/DNS+Privacy+Daemon+-+...
- politelemon 9y ago> for privacy, performance and security. I understand the privacy and security aspects. But I am wondering - how can DNS over HTTPS be more performant in the case of curl commands? A browser could probably persist the connection to the resolver and issue several requests together, but with a single curl command surely there's the overhead of initiating the first DNS resolve, the HTTPS connection, the second DNS resolve. There must be some delay compared to regular DNS. Side note - I just learned that performant is not a recognized word (https://english.stackexchange.com/questions/38945/what-is-wrong-with-the-word-performant https://english.stackexchange.com/questions/38945/what-is-wr...)
- CogitoCogito 9y ago> Side note - I just learned that performant is not a recognized word (https://english.stackexchange.com/questions/38945/what-is-wr... https://english.stackexchange.com/questions/38945/what-is-wr...) I don't personally use the word since there are many alternatives, but its use is now definitely widespread and consistently understood. There's really no argument against the fact that it has entered the English lexicon.
- metafunctor 9y agoCan anyone give examples of cases where “performant” would be better than “efficient”? To my mind, the difference is that “performant” delivers results quickly, whereas “efficient” uses little energy. A performant solution might be efficient, but not necessarily, and vice versa. Does anyone else share this understanding or am I living in a linguistic bubble? Not sure about Swedish (Daniel is Swedish), but in Finnish, we have the word “suorituskykyinen”, meaning “efficient” or “able to perform”. I can see how Finnish writers might want to use “performant” to replace this commonly used word. Perhaps there's a similar history for Swedish speakers? I sure have seen “performant” a lot in academic texts written by Finnish and Swedish speakers in the last 20 years.
- kodablah 9y ago"My mining algorithm, which uses a lot more CPU and memory, is more performant." The key being that performant is often associated w/ speed (i.e. higher performing) whereas efficient ambiguously can refer to many things you have improved on.
- metafunctor 9y agoYep, that's how I understand the word “performant” as well. A car that accelerates from 0-100 kph in under 3 seconds would be ”performant”. A car is “efficient” if it burns less than 4 liters of gasoline per 100 kilometers.
- vectorEQ 9y ago'performs more [efficiently|accuratley]' would be proper english (not that i speak it well.... :D). webster says: "performant" The word you've entered isn't in the dictionary. Click on a spelling suggestion below or try again using the search bar above. preformant performance performing performances performable preformants perforate conformant perform formant performed informant performer perforata performers performs preformat
- barrkel 9y agoThe algorithm doesn't perform more efficiently or accurately, though - it's less efficient (it uses more resources) and it should be the same accuracy (or we're comparing apples with oranges).
- userbinator 9y agoI don't use it either, and I agree with the poster on that stackexchange link about it sounding like manager/marketing-speak, but when I see it, it makes me pause for a second to think about what really means (perhaps that's the point) --- I had this exchange with a coworker not long ago: CW: ...and this way it'll be more performant too. Me: Performant? As in faster? CW: Yes. Me (to self): Then why didn't you just say it'll be faster? IMHO it obfuscates meaning and should be avoided; the surrounding discussion/vagueness about what it means (I don't think it means efficient, but only faster --- as in, a high-performance car) shows that too.
- molf 9y agoTo be fair, "faster" in the context of software development can also frequently refer to the time it takes to implement.
- pbhjpbhj 9y agoPerformant to me implies performing better against the relevant metrics. So faster, maybe, but perhaps smaller and more energy efficient too. If the context of the metrics is already understood then it seems quite a cromulent word.
- PakG1 9y agoWhat's cromulent mean? I looked it up at dictionary.com and couldn't find anything. Or are you making up more words to point out the irony? :)
- zimpenfish 9y agohttps://en.oxforddictionaries.com/definition/cromulent https://en.oxforddictionaries.com/definition/cromulent "Acceptable or adequate"
- timlyo 9y agohttp://www.dictionary.com/browse/cromulent http://www.dictionary.com/browse/cromulent
- karmakaze 9y agoGreat discussion. I've used the word without thinking twice. Now I'll choose between efficient, faster, or performant depending on context.
- coinerone 9y ago"Performant" is a word in German. It translates to exact what "perfomant" would mean in english if it were an english word. The funny thing is, google translate, translates the german word "performant" to the english word "performant". https://translate.google.com/?hl=de#de/en/per%C2%ADfor%C2%ADmant https://translate.google.com/?hl=de#de/en/per%C2%ADfor%C2%AD...
- deleted 9y ago[deleted]
- deleted 9y ago[deleted]
- nijaru 9y agoIt is not actually translating anything since performant is not considered a real word in English, although I commonly see it used in the tech world.
- SEMW 9y ago> performant is not considered a real word in English, although I commonly see it used... This is close to being a contradiction in terms. The purpose of words is to communicate, and if a word is being successfully used to communicate -- which clearly it is -- what exactly does it mean to say that isn't "considered a real word"? Also, "Considered" by whom? The dictionary? Dictionaries are descriptivist -- they record usage, they don't prescribe it [0]. If it isn't in the dictionary yet, that's only because the usage hasn't been used widely and/or for long enough that it meets the inclusion criteria [1]. (As it happens, "performant" is at the stage where it is starting to pass those thresholds, and is now in the OED [2]) [0] http://englishplus.com/news/news1100.htm http://englishplus.com/news/news1100.htm [1] http://public.oed.com/about/frequently-asked-questions/#qualify http://public.oed.com/about/frequently-asked-questions/#qual... [2] https://en.oxforddictionaries.com/definition/performant https://en.oxforddictionaries.com/definition/performant
- jfk13 9y ago
- yeukhon 9y agocURL supports it. See https://ec.haxx.se/usingcurl-persist.html https://ec.haxx.se/usingcurl-persist.html If your question is how to reuse the connection pool for, say, 1000 DNS queries from one machine, curl already uses a connection pool. Next, to use fewer TCP connections and get faster response, my first proposal is HTTP/2 which supports TCP multiplexing such that multiple requests can be issued over a single TCP connection. Every response is return asynchronously, we can achieve nonblocking. cURL also supports HTTP/2. Speaking of word: it seems author of curl project prefers “curl” over “cURL”? Worth asking.
- sapphire_tomb 9y agoFrom what I understand the "cURL" format of the word is popular mostly with users of the PHP bindings. "curl" is what the project uses, but I'm not sure they really care what other people refer to it as :)
- sohkamyung 9y agoI think it depends on whether you are referring to the project or the executable [1]: "cURL is the name of the project." [1] https://curl.haxx.se/docs/faq.html#What_is_cURL https://curl.haxx.se/docs/faq.html#What_is_cURL
- pilif 9y ago> Every response is return asynchronously, we can achieve nonblocking. same goes for UDP which DNS runs over normally. Like the original commenter, I fail to see how stacking DNS over HTTP over TLS over TCP over IP is going to be faster than running DNS over UDP over IP. Also, you still need to resolve the address of your DNS-over-HTTP server, which you'd probably still do over traditional DNS-over-UDP. This feels like doing nothing but adding complexity for zero gain.
- IshKebab 9y agoZero gain except going from easy eavesdropping, blocking, censoring, etc. to effectively unblockable, private and secure? Ok. Also you would probably need to put in the IP of the DNS server manually, exactly like you have to with DNS now.
- tscs37 9y agoIdeally the browser and curl only use a local resolver, on your machine or router, which in turn can use a steadily alive or even multiple alive connections to the resolver.
- geofft 9y agoIf your ISP is intercepting DNS requests and sending them to a slow or broken server, DNS over HTTPS ensures this won't happen. (Yes, they could block the traffic entirely, or slow it down for fun, but they can no longer intercept and redirect it.)
- nly 9y agoIt has zero performance advantages If you had to go the TLS route and wanted better perf, then it'd make more sense to build a new, dead simple, framing protocol that actually specified working pipelining and eliminated HOL blocking by allowing out-of-order responses. They're just using HTTP because HTTP(S) defaults to port 443 and it'll go through more firewalls, and I guess their thinking here is to (just add more complexity) and move to HTTP/2
- Franciscouzo 9y agoIt is a recognized word, at least by the Cambridge [0], Oxford [1], and Wiktionary [2] dictionaries. [0] https://dictionary.cambridge.org/dictionary/english/performant https://dictionary.cambridge.org/dictionary/english/performa... [1] https://en.oxforddictionaries.com/definition/performant https://en.oxforddictionaries.com/definition/performant [2] https://en.wiktionary.org/wiki/performant https://en.wiktionary.org/wiki/performant
- djrobstep 9y agoIf you recognize it, it's a recognized word. Dictionaries are descriptive, not prescriptive.
- tzahola 9y agoIsn’t this a chicken vs egg problem?
- jlgaddis 9y agoApparently: > "The DOH server is given with a host name that itself needs to be resolved. This initial resolve needs to be done by the native resolver before DOH kicks in."
- jayflux 9y agoYes and no, I think Google’s DNS over HTTPS service is run on 8.8.8.8 the same IP for their main dns service, so you should always know where it is. Edit: Looks like it’s changed and it’s now a url, so you’re right it is a bit chicken and egg
- dyu 9y agoYou can remember a small set of resolved hosts for this purpose, not unlike remembering DNS servers or CAs to trust. A quick search online also says it's possible to issue a cert to a public IP address, so you can also do HTTPS to a numbered IP instead of a host name.
- tzahola 9y agoI haven't heard of any respectable CAs that would issue certs for IP addresses...
- tialaramex 9y agoThey're rare but they do exist. The CA needs to ensure you really have long term control over the address. Most people would never need one, but a few people have a real use for them.
- Asooka 9y agoJust stick the address of the DNS resolver in /etc/hosts.
- zde 9y agoTo understand DNS, you must first understand DNS.
- chriszelazo 9y agoDNS is one of those things I have to reference every time. Definitely feels like this.
- averagewall 9y agoWhere does the privacy advantage come from? Once you resolve a hostname privately, don't you still need to use its IP address publicly for your traffic to be routed there?
- m_eiman 9y agoOne case where it might help is shared hosting: you don't know which of the domains hosted on that IP you're accessing. Narrows it down to just a few though, so IMHO not a big improvement.
- mschuster91 9y ago> One case where it might help is shared hosting: you don't know which of the domains hosted on that IP you're accessing. That depends on your level of access/monitoring: if it's just a firewall log that shows source/destination IP, then yes - but as soon as you have any kind of packet monitoring, then the domain can be easily sniffed from the SNI header.
- pbhjpbhj 9y agoYou'll need to mask page size if your trying to hide your access, even on a shared host with 100 domains I doubt you'll have pages where the byte-size isn't unique. I think with https the results were something like 90% of page access could be guessed using meta-data (see eg https://web.archive.org/web/20090308103611/http://sysd.org/stas/node/220 https://web.archive.org/web/20090308103611/http://sysd.org/s...). That's going to drop when you don't know the site but you're going to need more counter-measures to hide your access effectively.
- IshKebab 9y agoYes, but reverse DNS is not totally trivial (think AWS). Also current DNS can easily be MitM'd allowing attackers to insert JavaScript into web pages etc.
- kuschku 9y agoSo what use does this have? DNSSEC already gives us validation of the records, and thanks to SNI, this doesn't give us any privacy. It is more complex, more centralized, and ends up slower than using actual DNS, and doesn't seem to provide any benefits. Am I missing something?
- kodablah 9y agoEasier to prevent censoring. DNSSEC doesn't hide the fact that you're making a DNS call, correct? With HTTPS, censors/MITMs can only see the domain you go to. The censor/MITM won't know whether I went to google.com to search or perform DNS query. Plenty of countries have blocked DNS providers they don't like, now that's harder w/out also blocking the site as a whole.
- kuschku 9y agoEasier to prevent censoring from the ISP, but you're now just reliant on another company's systems. If you just want a solution for having a remote server execute DNS queries for you, you can just use any of the existing VPN protocols purely for DNS resolution, or even make a better performing version. All that overhead HTTP adds is wasted for this.
- kodablah 9y ago> All that overhead HTTP adds is wasted for this. When you're in an area where your DNS provider is limited by the state, you won't consider it wasted. But if you're not and you do consider it wasted, don't use it. But saying it doesn't seem to provide any benefit is wrong and just telling people to use a VPN for DNS resolution is also wrong (at least until the ergonomics improve).
- kuschku 9y agoIt's more a question why a company like Google would pay several engineers who are paid 6-digit sums to build this when they could build for the same or less much more powerful solutions.
- fpoling 9y agoI can see how DNS over HTTPS addresses security, but I do not see how it helps with privacy. After resolving the IP address over secure connection HTTPS still sends the host name unencrypted, so one can just eavesdrop on that. And if encrypted DNS becomes widespread, I suspect that various state-imposed firewalls like one Russia will just look for HTTPS connection header to block a particular site.
- tylerhou 9y ago> After resolving the IP address over secure connection HTTPS still sends the host name unencrypted Correct me if I'm wrong, but I'm pretty sure the host name is generally only sent in an HTTP header, which should be encrypted over HTTPS. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Host https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Ho...
- pjc50 9y agoNo, in order to multi-host SSL sites the host name has to be sent first in order for the correct certificate to be presented. https://en.wikipedia.org/wiki/Server_Name_Indication https://en.wikipedia.org/wiki/Server_Name_Indication
- deathanatos 9y agoYou don't even need SNI; the initial Server Hello, which contains the server's certificate (which contains the DNS name the certificate is issued for) is sent in the clear.
- tialaramex 9y agoNo longer true in TLS 1.3 as I understand it The ServerHello starts out by finishing key agreement and then (in the same message) it assumes its peer now knows the session key and encrypts the rest of the message, including Certificate.
- 9y ago
- Aissen 9y agoAnyone has good pointers on DNS over DTLS (draft RFC 8094) vs DNS over TLS (RFC 7858) vs DNS over HTTPS (this draft) ? And if you could throw in DNSSEC in the mix, that would be helpful.
- LogicX 9y agoWith pleasure - (CTO of DNSFilter, this is my world) DNS over DTLS (RFC 8094) speaks only to UDP This could be compared with DNSCrypt's implementation DNS over TLS (RFC 7858) is TCP focused DNS over HTTPs is focused on... you guessed it, HTTPs So all the same thing, all trying to add security and privacy, just over different transport mechanisms. While we're at it -- you did not mention DNS over QUIC: https://tools.ietf.org/id/draft-huitema-quic-dnsoquic-00.html https://tools.ietf.org/id/draft-huitema-quic-dnsoquic-00.htm... Some factors which start to come in to play with the various options are: Compatibility with firewalls and proxies (DNS over HTTPs wins, others over port 853 have a disadvantage, even if you put them on port 443, they may get stopped by deep packet inspection) TLS Improvement knobs: 0-RTT, TCP Fast Open, etc. (You can find a summary of these here: https://dnsprivacy.org/wiki/display/DP/DNS+Privacy+Implementation+Status https://dnsprivacy.org/wiki/display/DP/DNS+Privacy+Implement... ) And closely related, performance. It's tough to beat a lossy protocol with minimal overhead (UDP), but there have been a lot of improvements with Keep alive, eDNS0, pipelining, etc. We're currently doing a lot of testing around this, as we are working to offer useragents and LAN proxies implementing DNS over TLS, compared with DNSCrypt. Finally: DNSSEC. It lives in a different part of the 'security' spectrum here... The purpose of DNSSEC is to be able to authenticate the validity of an answer when traveling through untrusted parties (say you're using a third-party resolver, or do you trust your ISP's DNS to not mangle with responses). It does not encrypt request/responses. It does not provide privacy. It answers the question: "Can I trust this response I received for example.org to be the one that example.org intended me to receive?"
- Aissen 9y agoThanks, that's great! I didn't even know about dns-over-QUIC, but considering QUIC is still a draft itself… (I've been excited about it for quite a while though). Regarding middleboxes, I forgot about those, and it's very sad that they keep hindering progress this way.
- vectorEQ 9y agopeople invented other security things inside of dns protocol to avoid having the added bandwidth. i dont think it's reasonable to say that everyone can handle the increased load nowadays. However, i've been thinking of this, for enterprise, you could build a dns server which servers over TLS connections, and then put a local dns proxy on clients which receives on 127.0.0.1 and sends out tls to the custom dns server. That way any local network connections would be encrypted to passive listeners on the network. recursive queries would go onto the internet plaintext to 'normal' dns servers.
- Skunkleton 9y agoYou can already do this with existing tech. When a DHCP lease is acquired, you also get DNS server information. If you are concerned about the DNS packets being encrypted on your local network, then you can do that already as well by intercepting them with a local firewall and sending them across a tunnel. IMO, the purpose of DOH is to address semi hostile environments like the free Wifi at the Airport. It is kind of like a VPN for just your DNS traffic.
- alien_at_work 9y agoI really hope this doesn't catch on widely. It should be a tool for use where censorship issues can't be solved politically. Otherwise, why even have protocols at all? Just say the only protocol is HTTP. IP, etc. are just an HTTP implementation detail.
- banachtarski 9y agoI would love this to catch on wildly! DNS through TLS means it's all end-to-end encrypted, DNS reflection attacks are harder, etc. The "why even have protocols" doesn't make sense. Protocol can be layered just fine (HTTP itself is a good example). DNS as it exists now is another random special snowflake that vendors need corresponding snowflake implementations for.
- alien_at_work 9y ago>DNS through TLS means it's all end-to-end encrypted I didn't say I'm against DNS being encrypted, even with TLS. I just hate that instead of doing the right thing (e.g. political battle with the government, opening a port on a firewall) people choose the laziest way: just tunnel it over HTTP. >Protocol can be layered just fine (HTTP itself is a good example) They can, but why do it? Just figure out a way to make your server be yet-another-"REST"-service and pat yourself on the back for cleverness. >DNS as it exists now is another random special snowflake that vendors need corresponding snowflake implementations for. As is: SMTP, POP, IMAP, SSH, AMQP, FIX, SWIFT, LDAP, ODBC and a host of other protocols. Why do you use negative language like "random special snowflake that vendors need corresponding snowflake implementations for"? These are seperate protocols, which serve seperate specific needs. This is how IP was designed to work.
- BenjiWiebe 9y agoI guess someone just needs to do a VPN over HTTP. (Probably done already too)
- gkya 9y agoPolitical battles are hard to do, and take time, sometimes very very long times they take.
- stock_toaster 9y agoMaybe someone people will "rediscover" dnscurve.
- jedisct1 9y agoWhich is completely unrelated
- stock_toaster 9y agoIt isn't completely unrelated. DNSCurve secures the link between resolvers and authoritative servers. DNSCrypt (based on DNSCurve) secures the link between clients and resolvers.
- kabes 9y agoYou can also do http(s) over DNS: http://code.kryo.se/iodine/ http://code.kryo.se/iodine/ . Nice way to avoid paying captive portals, although probably not legal.
- gsich 9y agoWhy not?
- pbhjpbhj 9y agoIn USA and UK at least unauthorised access or use of a computer is criminalised. On some situations you can argue for assumed consent, the law doesn't operate on "if I can do it then it's authorised". Unless you can show you have permission then it's not authorised, ergo not legal. AIUI; not legal advice.
- gsich 9y agoBut the premise was to circumvent crap such as captive portals. Doing that on your own computer (mostly in a public wlan), I don't see any reason against it.
- remedan 9y agoYou're still circumventing security measures to use somebody else's hardware in a way they clearly don't want you to. That's illegal in most cases.
- gsich 9y agoWho is the "someone else" in your case? Where does the someone else's hardware come from? OP mentioned this to get rid off e.g captive portals. Iodine requires a client and a server. Both belong to you, what is the problem here? That I use a network to transmit packets? We are not talking about installing iodine on someone else's computer!
- jedisct1 9y agoDoH's great. I'm planning to write an Nginx module to support it soon.
- bandrami 9y agoActual DNS servers and clients have supported TLS since the early years of this decade. What's gained by adding HTTP transport overhead?
- est 9y agohttp is not overhead, http is the only transport that can go through middle boxes.
- throwaway2048 9y agoWhat dns servers and clients support TLS?
- bandrami 9y agoUnbound does it natively, and BIND and the rest use DNSCrypt's shim
- LogicX 9y agoWhile we at DNSFilter are working on support of DNSCrypt, just to add some flavor to your note... it should be mentioned that the original author just abandoned the project, removed the repos from his github user, shut down the website, and it's been setup by a few industry players under a new github org: https://github.com/DNSCrypt https://github.com/DNSCrypt Tough to say what direction the project will take. I for one welcome other advancements such as Google's efforts. FWIW, my understanding is if you use Chrome it actually communicates over QUIC
- mosselman 9y ago“...for privacy...” and “Google runs one...” Strikes me as funny. Interesting concept apart from this detail though. Are there any servers that aren’t owned by advertisers and the like?
- datawarrior 9y agoYes. A lot of the major data centers provide free DNS. Even verizon does. Here is a somewhat decent list: https://www.lifewire.com/free-and-public-dns-servers-2626062 https://www.lifewire.com/free-and-public-dns-servers-2626062 You can also just run your own too. I run one from a VPS.
- Skunkleton 9y agoYou could stand up your own server. It isn't that hard or expensive.
- aplorbust 9y agohttps://stat.ripe.net/data/dns-chain/data.json?resource=example.net https://stat.ripe.net/data/dns-chain/data.json?resource=exam... https://dns-lg.sidnlabs.nl/example.com/A https://dns-lg.sidnlabs.nl/example.com/A
- philip1209 9y agoWe prototyped this as an intern project at OpenDNS, too: https://github.com/opendns/OpenResolve https://github.com/opendns/OpenResolve We mostly built it because it sounded cool, but one use case that I though was important was being able to boot these images in different data centers to collect telemetry on DNS differences geographically (eg for hijacking or anycast).
- LogicX 9y agoNice project! We at DNSFilter are able to collect that same telemetry just by having resolvers at each of the anycast locations -- between the different locations, and passing along eDNS Client Subnet information, many responses will be (legitimately) different. A little hard to see a hijack in that noise.
- wannabeinggeek 9y agoI am just wondering why would you want DNS over https instead of something like dnscrypt which would be dns over ssl ( I think opendns does this already) ?
- icebraining 9y agoMy guess is meddling corporate firewalls that spy on SSL/TLS traffic (using custom certs installed on the machines) and block unrecognized traffic.
- datawarrior 9y agoBut this wouldn't prevent that at all. They'd still be decrypting the traffic on HTTPS. What you're describing is a proxy issue not a DNS resolution one.
- Panino 9y agoDNSCrypt doesn't use SSL or TLS. You may have assumed that because DNSCrypt defaults to 443/TCP but that is only for availability, as this port is usually not blocked. The packet format is very similar to DNSCurve, from which it descends.
- nly 9y agoI've been pushing all my DNS traffic over a VPN, transparently, for the whole house, for years now (by setting the VPN remote IP as the upstream resolver on my router). It seems the only advantage of DNS-over-HTTPS is that it does DNS over TLS on port 443, which is harder for militant netadmins to block. It's definitely a solution to a niche problem, but if we really want to encrypt DNS at scale then we could do it easily enough by introducing DNScurve to the SOHO market.
- quacker 9y agoDNS through a VPN is only a partial solution though, right? Even if there's a recursive/caching resolver within the VPN (so _my_ direct DNS requests are private) any DNS requests outbound from the VPN go through global DNS. But, I guess same problem for DNS-over-HTTPS currently.
- LogicX 9y agoCorrect -- there's not currently any standard for recursive resolvers to communicate securely to authoritative providers. We'd like to change that.
- DavideNL 9y agoWhen you run DNS requests over VPN, you are sharing your "browsing history" with (at least) 1 other third party: whoever runs the VPN server, and whoever runs the (public) DNS server. Your ISP can see the IPs you connect to regardless of whether you use your ISPs DNS server or not (unless of course you tunnel ALL traffic of all clients through the vpn as well.)
- nly 9y agoIt's low hanging fruit. Logging DNS queries is a lot cheaper for an ISP than filtering out and logging SNI entries in TLS handshakes.
- fouc 9y agoI'm wondering if libcurl supporting custom DNS resolvers could make it easier to explore alternative DNS systems like namecoin.
- hollander 9y agoOpenDNS used to offer a secure DNS-tool. I can't find it anymore. Maybe Cisco removed it? Why can't we use something like that?
- LogicX 9y agoYou're thinking of DNSCrypt. It unfortunately was recently abandoned by the original developer. Some folks have mirrored it here: https://github.com/DNSCrypt https://github.com/DNSCrypt
- okneil 9y agoAs a mac user, how can I set this up locally to run all my DNS over TLS?
- throwme_1980 9y agolol
- kernelPan1c 9y agoYes, greater for security but still depends upon reliability of certificate authorities and ISPs. ISPs have the ability to issue the client a bogus certificate while they hold the real one in order to decrypt traffic. Why won't browsers allow the certificate's public key to be readable by javascript so that the remote server can verify the client has the correct certificate? This wouldn't be foolproof but it would significantly beef up security. Similar to how tor hidden services get resolved, distributed hash tables seem like the way to go. Take the ISPs and Cert Authorities out of the equation.
- gcr 9y agoI thought modern browsers ship with pinned certificates for Google and other large companies built in to the browser download.
- kernelPan1c 9y agoPublic key pinning helps but it operates on the assumption that the initial key is the correct one. I find it curious that these public keys are not readable by the client.
- Someone1234 9y ago> Why won't browsers allow the certificate's public key to be readable by javascript Because sites would randomly block reverse proxies, web proxies, enterprise users, people using certain WiFi APs, and it would give advertisers another thing to track users on. Frankly after looking at what websites did with the User Agent, I'm scared to see what they'd do when a certificate mismatch occurs.
- nly 9y agoMaking the public key of the remote available to JS wouldnt help because if you can't trust the identity of the remote server or integrity of the connection then you can't trust the javascript. Tor hidden services are secure because of the lack of human meaningful names. See: https://en.wikipedia.org/wiki/Zooko%27s_triangle https://en.wikipedia.org/wiki/Zooko%27s_triangle
- aplorbust 9y ago"Do DNS resolves over HTTPS for privacy, performance and security. Also makes it easier to use a name server of your choice instead of the one configured for your system." "A server that is acting both as a normal web server and a DNS API server is in a position to choose which DNS names it forces a client to resolve (through its web service) and also be the one to answer those queries (through its DNS API service)." https://tools.ietf.org/html/draft-ietf-doh-dns-over-https-02 https://tools.ietf.org/html/draft-ietf-doh-dns-over-https-02 How might this affect users who block ads via DNS? What about users who want the system DNS settings they have configured (e.g. /etc/resolv.conf) to be honoured? I can clear browser DNS cache with a couple of keystrokes, but I am not using Chrome, Firefox, IE/Edge, Safari, Brave, Opera, etc. How easy is it for a user to clear the DNS cache in the popular browsers? The best "privacy, performance and security" for the user is achieved by using /etc/hosts. HOSTS (i.e., no DNS) will beat DNS on all three, every time. "Flexibility" was not mentioned as a criteria. There is also the issue of "transparency" to consider. It is easy for the user to check their HOSTS file to see what are the current name to address mappings. How easy is it for the user to check what mappings are in the browsers DNS cache? Fact: Many/most of the names looked up by a user repeatedly every day do not change by the hour, by the day, the week, month or even year. As a user, I use HOSTS heavily, with appropriate ed scripts for fast automated modification. I use HOSTS for the transparency, control and speed. Any privacy or security benefit is a bonus. Contrast: https://en.wikipedia.org/wiki/Fast_flux https://en.wikipedia.org/wiki/Fast_flux (need DNS or perhaps "DOH" for this to work)
- pas 9y ago> How might this affect users who block ads via DNS? They should make sure to use a trusted DNS over HTTPS resolver.
- Zash 9y agoMust everything be over HTTPS? Must all diversity really be killed like this? It saddens me.
- breatheoften 9y agoI hate the idea of ad networks using this ...