16 ms·
Inside Firefox’s DNS-over-HTTPS engine
- textmode 8y ago"Caveats TRR doesn't read or care about /etc/hosts There's no way to exclude or white list specific domains" For me, the primary advantage of HOSTS/DNS is the ability to control answers to application queries for addresses and block ads. This seems to remove all control a user might have through controlling such lookups. Yikes. I think DOH is useful but in a different way. For example, it is useful for retrieving bulk DNS data using RFC 2616 pipelining, alleviating dependence on piecemeal DNS lookups, thus increasing speed and privacy. Data can be stored locally and refreshed periodically, if necessary (I have been doing this witout problems for 15 years). It's also useful for retrieving data from a variety of caches, allowing answers to be compared.
- niftich 8y agoFirefox's DOH client ignores /etc/hosts, but it shouldn't be too hard to host your own DOH server [1][2] that you could then configure how you see fit. I can see this pattern becoming widespread someday, and with DOH, people can re-use their experience in setting up webservers. [1] https://github.com/st3fan/tinydoh https://github.com/st3fan/tinydoh [2] https://github.com/m13253/dns-over-https https://github.com/m13253/dns-over-https
- toomuchtodo 8y agoI think there’s great value in DOH caching servers running on home routers; all the benefits of DOH but “regular DNS” between clients and your home router.
- peterwwillis 8y agoYou think regular end users having to set up and maintain server software in order to force a name for an IP is going to become a widespread pattern? That's horrifying. I don't want to live in that world.
- greglindahl 8y agoRegular users today don't use that feature, so you're choosing a rather odd hill to die on. To put this another way: it's a significant benefit for my random non-techie friends to be able to use this new feature plus HTTPSEverywhere. And even as a techie, I don't use a hosts file to block anything. So I'm not bothered by how Firefox chose to implement this, like most people.
- da_chicken 8y agoThere's plenty of ad blocking, spyware blocking, ransomware blocking, etc. software that absolutely uses the hosts file to blackhole requests. Much of it is free and intended for home computer use.
- greglindahl 8y agoAnd what market share do they have? None of my non-techie relatives or friends who've asked me to look at their machines run that kind of software.
- mortenlarsen 8y agoOnly the use case with the largest market share matters? That kind of thinking, really irks me.
- greglindahl 8y agoNo, I don't think like that. It does bother me when Firefox introduces a feature which covers up a huge hole in TLS, and they get a large number of complaints on HN.
- vetinari 8y agoOf course it gets large number of complains, when it creates more problems than it solves, and it is papered over "but mainstream users do not need that". Mainstream users do not need most software ever made.
- fanf2 8y agoThat [1] implements a very old draft so I doubt it is compatible with Firefox.
- chupasaurus 8y agoJust run local dnscrypt-proxy (it supports DoH) on your machine/router and everything would be fine.
- deleted 8y ago[deleted]
- dogecoinbase 8y agoTRR doesn't read or care about /etc/hosts There's no way to exclude or white list specific domains Sigh. This is aggressively breaking normal DNS behavior (and will be an absurd hassle for a very large number of organizations, but in terms of extremely normal split-horizon and orgs with regulatory obligations to catch HTTPS traffic). Applications should not contain their own encapsulated resolvers, let alone resolvers that default to sending all of my DNS traffic to for-profit companies that have previously experienced massive data leaks (and fun CF fact, they invited the then-CTO of Cambridge Analytica to talk at their Internet Summit event in SF last year).
- riquito 8y ago> will be an absurd hassle for a very large number of organizations they can disable it, any organization that modify /etc/hosts can also change Firefox's preferences file
- peterwwillis 8y agoThis isn't an acceptable compromise. In general it's not acceptable to break functionality and then demand people invent workarounds. But it's insane to demand that every organization in the world write new portable system integration software that has to take into account 100 varying things just to disable something nobody has asked for. And it's even more insane when the software in question is the underpinning of all internet access that has existed in the same form for 40 years.
- greglindahl 8y agoI wanted this feature.
- dogecoinbase 8y agoNo, you wanted encryption for DNS transport, and I completely agree with that desire. This is a terrible half-measure that bypasses many existing security precautions people have intentionally taken by default, and moreover exposes private data to a company with a history of handling such poorly.
- acqq 8y agoAlso problematic: "0 - Off (default). use standard native resolving" ... "5 - Explicitly off. Also off, but selected off by choice and not default." It seems that the plan for the "0 - default" is to switch the users to other modes without the user knowing it, and to keep the behavior off the user must specifically change the option to "5."
- anonymfus 8y agoNo, it is not problematic, it's a good engineering. Imagine in the future DNS over HTTPS will be supported by OS and there will be an OS-wide setting for it. Then it will make sense to change default setting in FireFox to use OS-wide setting.
- bagder 8y ago"I better speculate on the reason here because surely Daniel is part of a conspiracy meant destroy the browsing experience of millions" or... It could be prepared for when the user gets asked what they want and then Firefox can remember an explicit "no" as compared to not selection ever made. / Daniel (author of the blog post)
- acqq 8y agoDaniel is not responsible for the decisions made by other Mozilla managers who already used their powers to deliver an unsolicited ad to the millions using the means presented as having apparently other purposes. Daniel’s own decisions aren’t in question here. If he works for Mozilla he is not more powerful than the whole company. Having “off” and “off when selected by user” but not other variants still points to the intention of the default state not remaining off. Which is not problematic. Problematic is however naming the state that will obviously be changed “off.”
- Operyl 8y agoIt’s worth noting that Daniel is the GP here. You’re talking about him in the third person.
- oger 8y agoNice job Daniel (again...)! While TRR only sounds very appealing for certain threat vectors the handling of captive portals is still a ‚nasty‘ thing. While certainly not in the realm of DNS over HTTPS the logic / UX on the browser side as well as interaction with the underlying OS definitely needs improvement.
- bagder 8y agoThanks! Captive portals are indeed truly complicated beasts to handle and they offer challenging obstacles for browsers (and others). We keep working on trying to improve how Firefox detects and works with them.
- gkya 8y agoIs there a particular reason a DNS resolver should be implemented in a web browser? Wouldn't it be better if it was a system-wide configuration?
- joelthelion 8y agoIt's been 30 years and DNS is still a major security and confidentiality flaw in all widely used OSes. I welcome my browser doing something about it. If in the future OSes and ISPs provide better alternatives, this feature can always be turned off.
- gsich 8y agoIt is default off.
- Operyl 8y agoFor now. In the future it won’t be from what I understand.
- gkya 8y agoI do want to use this on all my devices, not that I'm criticising the DoH concept per se. Only that it seems to me that the browser is not the correct place for the DNS resolver; thus I wonder why it's not the OS but the browser that gets the new features.
- effie 8y agoOne reason could be that large number of users of web have no real power to set up their operating system to use their preferred DNS server (e.g. non-technical employees in many big corps). The present-day OSes are designed to favor the administrator and to restrict the users.
- jlgaddis 8y ago> (e.g. non-technical employees in many big corps) IMO, employees should be using whatever their organization has configured for them -- not whatever they wish. A "regular user" changing the DNS servers on his work PC (joined to an Active Directory domain) to 8.8.8.8, for example, WILL run into problems at some point. They say they have workarounds for this but I think it's safe to say that bugs will likely be found. In the meantime, things will be broken for those users. Moving this setting into the web browser (where it likely CAN be changed by a user) is not the proper solution.
- codewithcheese 8y agoI am in Indonesia where Reddit, Vimeo, The Pirate Bay and other sites are blocked. I just enabled TRR in Firefox 60 (They mention best support is in 62) and now I have full unblocked access to all those sites. Awesome.
- dtech 8y agoUsing an alternative DNS resolver like 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare) could solve that already, and not only in Firefox.
- gsich 8y agoOr Quad9, but this could be intercepted.
- xorcist 8y agoapt-get install unbound
- stordoff 8y agoIt depends how the block is implemented. If it's done by intercepting DNS requests, it doesn't matter what server you _try_ to reach. There's also the Virgin (UK) approach of allowing the correct DNS response, but tampering with HTTP requests (though switching to DNS-over-HTTPS wouldn't help in that case).
- flamemyst 8y agoThat will not work. Some ISP do DNS transparent proxy (forward all udp packet 53 to their own DNS server). You need DNSCrypt or VPN.
- eknkc 8y agoThey generally inspect DNS packets and block hostnames from resolving correctly. Does not matter the destination.
- codewithcheese 8y ago
- valarauca1 8y agothis states it bypasses my local resolver. Does it still account for /etc/hosts blocks? I use a few thousand entries to black hole malware and ad networks and I’d rather not lose this.
- navlelo 8y agoIn the caveats section it says that it is ignored
- yardstick 8y agoThey have options to tweak soo many other aspects of TRR/DOH, why can’t they add an option to support /etc/hosts?
- zaarn 8y agoIt's probably on a todo list somewhere. The difficulty there, I believe, is that /etc/hosts is commonly parsed by your libc, so firefox will have to reimplement /etc/host parsing on top of their libc if it does not expose /etc/host entries in some way (glibc and muslc both don't to my knowledge)
- codedokode 8y agoEncrypted DNS is great, but please also do something with SNI. I am sure other users don't want their ISP to peek at what sites they are visiting too.
- bagder 8y ago... that's why the article you're commenting on mentions SNI and that we hope to address that too (but separately) going forward!
- codedokode 8y agoAlso I thought that IPv6 doesn't need SNI, because with it you can allocate a separate IPv6 address for each service.
- xorcist 8y agoThat doesn't help privacy, as you could just connect to those addresses and see what certificate they present.
- xg15 8y ago> It also makes it easy to use a name server of your choice for a particular application instead of the one configured globally (often by someone else) for your entire system. I can see app developers wanting this, but as a user, I really hope, this doesn't happen. It's bad enough that many applications today manage their own certificate stores, making the next part of internet infrastructure app-specific seems to me a way to more fragmentation and less understanding or oversight I'd have over my own system.
- effie 8y agoThe intent is good - to give users of the applications more power in their relation with their employer and state, similarly to what the GNU project and the GNU Hurd kernel promote. Of course, there is danger that develepers will misuse this and hardwire their preferred DNS into their application. If this becomes a problem, the users will have to either reject the application or apply some MITM remedy.
- tialaramex 8y agoIf anything we want _more_ trust stores rather than less, although I'd certainly take "uses the latest Mozilla NSS trust store" over "I pasted in this list I found on the Internet fifteen years ago and have never updated it" in most applications. One reason to desire separate trust stores is that your model of trust is almost certainly not "I wish my application trusted exactly the same CAs as [say] the Firefox web browser and I will incorporate all the same special rules and exception as that browser". Example: Back in 2016 the US government expressed interest in operating its own public CA. This probably won't happen under Trump of course, but in Firefox this would have been no problem if they met its other criteria, it's easily able to accept a new CA and apply constraints to it. So that in Firefox a US Federal Web PKI cert for whitehouse.gov works, but one for gov.uk or google.com does not. But does your application have that logic? Or would it just blindly trust the new CA because Mozilla added it to their trust store? The other reason is that your application is (especially if you aren't on the ball enough to run your own trust store) probably not able to keep up with the security treadmill, and falling off may be painful. Example: If your system depended upon SHA-1 certificates to function, but you used the Web PKI CAs from somewhere like Mozilla's NSS store, magically in 2016 no more new certificates were available. No problem for the browser vendors, they had voted for exactly this outcome. Too bad for your application.
- ksec 8y agoAm I seeing this as another huge opportunity for CDN like Cloudflare and Fastly? Although I am not too comfortable with everything moving to HTTP. HTTP 2 was already complex enough, it seems we want to move everything into HTTP, everything away from TCP to UDP. What happen to QUIC anyway ?
- Operyl 8y agoThere’s a working group for it that’s bashing out ideas, but I haven’t heard much from it in a while. I recall hearing they’re trying to take the parts they want and merge them into HTTP2.
- tialaramex 8y agoThe IETF has a QUIC Working Group. If you have relevant skills you should definitely join it. https://datatracker.ietf.org/wg/quic/about/ https://datatracker.ietf.org/wg/quic/about/
- KenanSulayman 8y ago> [..] DOH increases privacy, security and sometimes even performance [..] Does anyone know how TLS over TCP can be faster than UDP?
- kevincox 8y agoI believe that big DNS responses will be faster because instead of establishing a TCP connection there is already a warm one ready to go. But yes, for the common case the performance will be the same.
- CarlHoerberg 8y ago> This initial approach, at least, does not cache the intermediate CNAMEs nor does it care about the CNAME TTL values. That's a total violation of the standard and will break A LOT of things. Example: my.domain.com -> CNAME ec2-1-2-3-4.aws.com 30s TTL -> A 1.2.3.4 30days TTL. So Firefox will now cache my.domain.com to 1.2.3.4 for 30 days? When you update the record for my.domain.com the change today will be applied in 30s, but with this flawed heuristic it won't expire until after 30 days.
- snvzz 8y agoI'm strongly against this. Bypassing the system's DNS is a no-go. If this passes, it's going to be a nightmare to system administrators. Basically, each and every split horizon will be broken. But, promoting DNS-over-HTTPS in the browser and providing an easy-to-install, separate tool for Windows/OSX to solve through DNS-over-HTTPS is something I could get behind. Like how on my network I do use dnscrypt-proxy, so everything is already using DNS-over-HTTPS.
- mike-cardwell 8y agoI don't like the idea of this, but even the implementation is bad. If we're going to do DNS over HTTPS, then there should be a standalone application, and the system should be reconfigured to use it, so all running applications on the system use it. I mean, do we really want all of our desktop applications to have their own built in custom ways of mapping domain names to IP addresses? [edit] E.g on Linux, it could install an application with a DNS interface listening on localhost port 53, which would then convert the request into a "DNS over HTTPS" request, and resolv.conf would be updated to use that resolver.
- madmax96 8y agoTotally agree re: implementation details. And, like you said, this is a bad idea. Is there something wrong with efforts like DNSCrypt + DNSSec? That's supposed to provide authentication and encryption to DNS without sending everything over HTTP. Did Mozilla just totally ignore the work that's already been done in this area?
- HurrdurrHodor 8y agoJust a guess but maybe they wanted to build this in a way that it would actually get used.
- mike-cardwell 8y agoThere's no reason that Firefox couldn't check for the existence of a local DOH resolver, and if it doesn't see one, pop up a one time message offering to install one for you. Every operating system has a system wide way of resolving names to IP addresses, and every application uses it. This new architecture of building custom name resolution into individual applications might be easier for them to build, but it's crap.
- madmax96 8y agoThat doesn't address my concerns, actually. Mozilla is doing two things: 1. Bundling DNS with the browser (e.g. ignoring system DNS) 2. Using DNS over HTTPS Mozilla could still do (1) and then use DNSCrypt + DNSSEC internally. Then, it would actually be used, but they'd be relying on existing technology that actually fits the use-case, rather than DNS-over-HTTPS. For the record, I don't think you should ignore the system's DNS, either.
- j0057 8y agoI'm not very happy we're now going to send all DNS traffic to 6 centralized DNS-over-HTTPS servers[1]. We can't trust our ISP, but we can trust Google and Cloudflare? I also noticed that when I configure my Android's proxy settings to point at a Privoxy container that routes through a VPN, I still get DNS-hijacked to my provider's "thepiratebay.org has been blocked for you" page -- this only happens in Chrome mobile, not Firefox mobile. I was used to DNS resolving through the proxy server. [1] https://github.com/curl/curl/wiki/DNS-over-HTTPS#publicly-available-servers https://github.com/curl/curl/wiki/DNS-over-HTTPS#publicly-av...
- sp332 8y agoMozilla actually has a contract with CloudFlare to protect user data. It's stricter than CF's normal privacy policy which applies to other users of the DNS-over-HTTPS service. Only 3 types of aggregate information will be kept for more than 24 hours. https://developers.cloudflare.com/1.1.1.1/commitment-to-privacy/privacy-policy/firefox/ https://developers.cloudflare.com/1.1.1.1/commitment-to-priv...
- ectospheno 8y agoThe good news is that blocking traffic to those six servers is trivial. You can stick the rule right after the one blocking traffic to port 853.
- apatters 8y agoThat depends on your use case. If you live in a country where you could be prosecuted for making a DNS request to a politically sensitive website, yeah, you're probably better off trusting Google with your DNS history.
- jontro 8y agoAt least there could be a user configurable black list for known split-horizon domains.
- cm2187 8y agoWhat kind of headers get transmitted as part of the DNS query? With DNS, the nice thing is that it is not a chatty protocol, no authentication, no cookies, no user agent. https is exactly the opposite. It would be nice to know that it is not a new backdoor into tracking people. [edit]: plus isn't Stateless TLS Session Resumption effectively a cookie?
- jedisct1 8y agoTLS tickets are indeed a kind of a cookie. Even without tickets, having TCP sessions means that server operators can link multiple queries to a single device, even if multiple devices share the same external IP. This gives server operators more data than plain DNS. The DNSCrypt protocol can use a unique key for every query in order to prevent this. Since it doesn't use sessions, and all queries are independent, there is no latency overhead. For DoH, dnscrypt-proxy has an option to disable TLS session resumption. But it introduces some overhead every time a reconnection is necessary.
- davidu 8y agoThis further drives centralization of the Internet and the idea that the Internet == Web == Browser. It's disappointing to see this coming from someone so steeped in Internet contributions and history and believing it to be a good idea. Bypassing system DNS is not just an enterprise no-go, it probably will end up reducing privacy. The idea that ISPs sniff DNS is largely a red-herring, and further it's already easily addressed by DNSCrypt or DNS over (d)TLS.
- dannyw 8y agoMy ISP in Australia already censors various domain names due to copyright lawsuits. ISPs tampering with DNS is not a red herring, but a real issue. Furthermore, ISPs in some countries like India forces all port 53 traffic to their own censored servers. DNS over TLS won’t solve that.
- adrianmonk 8y ago> It also makes it easy to use a name server of your choice for a particular application instead of the one configured globally (often by someone else) for your entire system. While I'm sure it's true that Firefox's implementation does this (presumably it provides a setting in the UI whereas it didn't before), there was nothing preventing this with regular DNS. It isn't something that DNS-over-HTTPS makes possible. Specifying your own DNS server instead of using the system default is a feature that the nslookup command has offered for like 25 or 30 years, so I'm sure a web browser could offer it too.
- textmode 8y agoHere is a brief demonstration of how "DOH DNS servers" can be useful. Nevermind the idea of applications having their own DNS caches. 1. fetch page of html, e.g., hn front page curl https://news.ycombinator.com > 1.htm 2. extract urls from 1.htm yyt < 1.htm > 1.txt (example scanner "yyt" provided below as t.l) 3. convert urls to hostnames g=1.txt k 1 (example script provided below as "1.k") 4. retrieve json dns data from doh dns server, efficiently, over a single connection see https://news.ycombinator.com/item?id=17228745 5. convert json dns data to csv see https://news.ycombinator.com/item?id=17228473 6. import csv into database e.g. sqlite3, kdb+, export to /etc/hosts, export to zonefile for localhost auth dns server, etc. now, when user is reading hn front page, no dns lookups are needed. user already has the dns data. there is no network usage for dns requests, increasing hn front page browsing speed for the user. there are no piecemeal dns requests sent, increasing user privacy. 7. track ip address changes over time, compare answers from different caches, etc. retrieve type 2 (NS) instead of type 1 (A) records, then compare to NS records provided in public zonefiles from icann, public internet scans, etc. cat t.l #define p printf("%s\n",yytext); %% \200|\201|\204|\223|\224|\230|\231|\234|\235 http:\/\/[^ \n\r<>"#'|]* p; https:\/\/[^ \n\r<>"#'|]* p; ftp:\/\/[^ \n\r<>"#'|]* p; .|\n %% int main(){ yylex();} int yywrap(){} /* compile with something like: flex -Crfa -8 -i t.l cc -pipe lex.yy.c -static -o yyt */ cat 1.k /k3 (novice level) /usage: g=f k 1 where f is list of urls h0:_getenv "g";h1:0:h0; h1:{:[(#h1[x] _ss "://")>0;h1[x];_exit 1]}'!#h1;h1:{*((h1[x] _ss "://[^/]")+3) _ h1[x]}'!#h1;h2:{h1[x] _ss "[^a-z^A-Z^0-9^.^-]"};h3:{*h2[x]};h1:{h3[x]#h1[x]}'!#h1;h1:?:/h1;h0 0:h1; \\
- textmode 8y agocorrection to 1.k: delete empty line 1 from list of hostnames / novice alert. this is probably 3x larger than necessary h0:_getenv "g";h1:0:h0;h1:{:[(#h1[x] _ss "://")>0;h1[x];_exit 1]}'!#h1;h1:{*((h1[x] _ss "://[^/]")+3) _ h1[x]}'!#h1;h2:{h1[x] _ss "[^a-z^A-Z^0-9^.^-]"};h3:{*h2[x]};h1:{h3[x]#h1[x]}'!#h1;h1:?:/h1;if[0=#h1[0];h1:h1 _di 0];h0 0:h1; \\
- textmode 8y agoftp -4o 1.htm $1; fetch -4o 1.htm $1; wget -4o 1.htm $1; curl -4o 1.htm $1; exec k 1d \ |exec tcs cloudflare-dns.com cloudflare-dns.com >1.json; yyf < 1.json >1.csv; #t=list exec k j; #t=hosts exec k j; t=db exec k j >1.csv; #t=zone exec k j; \\ k).Q.fs[{`t insert +:`ts`ip`hn!("ZSS";",")0:x}]`:1.csv k)t \\ / 1d.k / urls, hosts a:0:"1.htm"; a:,/$a; a:_ssr[a;"\42";""]; a:_ssr[a;"http://";"https://"]; a:_ssr[a;"src=//";"https://"]; b:a _ss "https://"; a:b _ a; b:{a[x] _ss "[^a-z^A-Z^0-9^.^-]"}'!#a / fail: https://example.com- c:{1#(3_ b[x])}'!#b; b:{c[x]#a[x]}'!#c; b:?:/b; b:{8_ b[x] }'!#b; / http a:"GET /dns-query?ct=application/dns-json&name="; c:"&type=1 HTTP/1.1\r\nHost: cloudflare-dns.com\r\nConnection: "; d:"keep-alive"; e:"close"; f:"\r\n\r\n"; g:(#b)-1; h:{a,b[x],c,d,f}'!g; i:a,b[g],c,e,f; `0:,/$h,i; \\ int main(int argc, char **argv){ char *b[17]; b[0]="/usr/bin/openssl"; b[1]="s_client"; b[2]="-tls1_2"; b[3]="-no_ssl2"; b[4]="-no_ssl3"; b[5]="-ign_eof"; b[6]="-no_ticket"; b[7]="-tlsextdebug"; b[8]="-servername"; b[9]=argv[2]; b[10]="-verify"; b[11]="9"; /* -host, -port removed from manual */ /* but still found in s_client.c */ b[12]="-host"; b[13]=argv[1]; b[14]="-port"; b[15]="443"; b[16]=(void *)0; execve("/usr/bin/openssl",b,(void *)0); } /j.k j:("SSSSSS";",")0:"1.csv"; k:_getenv "t"; if[k _sm "list";`0:{,/$j[4;x]}'!#j[5]]; if[k _sm "hosts";`0:{,/$j[5;x]," ",j[4;x]}'!#j[5]]; if[k _sm "db";`0:{,/$j[2;x],".",j[1;x],".",j[0;x],"T",j[3;x],",",j[5;x],",",j[4;x]}'!#j[2]]; if[k _sm "zone";`0:{,/$".",j[4;x],"\n&",j[4;x],".:127.0.0.1:5\n=",j[4;x],".:",j[5;x],":5"}'!#j[2]]; \\ \\ /* f.l */ #define echo ECHO #define jmp BEGIN #define p printf #define nl p("\n") #define s p(",") %s xa xb xc xd xx xy xz xa "\"Question\":[{\"name\": \"" ya ", \"type\": 1}]," x1 "\"type\": 1" x0 "\"type\": "[^1]"," yb "\"data\": \"" xw "Date: " xx \"\},\{\" xy \"\}\]\} xz "Sun, "|"Mon, "|"Tues, "|"Wed, "|"Thu, "|"Fri, "|"Sat, " %% {xw} jmp xz; <xz>"GMT" jmp xy; <xz>{xz} <xz>" Jan " p(",01,"); <xz>" Feb " p(",02,"); <xz>" Mar " p(",03,"); <xz>" Apr " p(",04,"); <xz>" May " p(",05,"); <xz>" Jun " p(",06,"); <xz>" Jul " p(",07,"); <xz>" Aug " p(",08,"); <xz>" Sep " p(",09,"); <xz>" Oct " p(",10,"); <xz>" Nov " p(",11,"); <xz>" Dec " p(",12,"); <xz>\40 s; <xz>. echo; <xy>{xa} jmp xa; <xa>{ya} s;jmp xb; <xa>\.\" <xa>. echo; <xb>{x0} jmp xx; <xx>{xy} nl;jmp 0; <xx>{xx} jmp xb; <xb>{x1} jmp xc; <xb>. <xc>{yb} jmp xd; <xc>. <xd>\"\} nl;jmp 0; <xd>. echo; \n . %% int main(){ yylex();} int yywrap(){}
- amaccuish 8y agoSo how does this work with my internal active directory running DNS? I assume firefox is clever enough to at least note the DHCP domain. I still don't like the idea this could mess with my private name resolution. Also will the end goal be to have a new DHCP option so I can point my clients to my internal DOH server? One of the nice things about this is I can make lookups authenticate. I hope the extend the update protocol into the HTTP context so we have a simple API for updating zones rather than nsupdate.
- jlgaddis 8y agoUsing Firefox 60.0.1 on Fedora 28, I just went into "about:config" and set "network.trr.mode" to "5" [0] since 1) I intentionally have local DNS servers that I wish to use and 2) I do not wish to send any more of my data to Cloudflare (as much as possible). I thought this might be a good way to ensure that this behavior does not get turned on without my knowledge (whenever the time comes that Mozilla enables it by default). Unfortunately, browsing broke immediately. I could not access any sites that I tried to access ("Hmm. We’re having trouble finding that site.") until I changed this setting back to the default ("0"). [0]: "Explicitly off. Also off, but selected off by choice and not default."