From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Should we block DoH by default?
Date: Tue, 03 Mar 2020 18:32:00 +0000 [thread overview]
Message-ID: <1d0ca483-76bf-9588-a836-4344e5c14342@ipfire.org> (raw)
In-Reply-To: <596BD1FF-1BCB-4184-A92C-86F19E6104FD@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2304 bytes --]
Hello Michael,
thanks for your reply.
I like your suggestion, and see something like "reject any client
connecting to any other DNS server on the internet" similar to blocking
outbound connections to port 25 in order to prevent spamming.
In both cases and for most SOHO networks, there is little legitimate
reason to do so. Regarding external DNS servers, IoT and similar things
come to my mind, which have their resolvers hard-coded in the firmware.
What do we do about any other DoH server on the internet? I guess filtering
these is hopeless, as censorship circumvention is one of its design goals,
but at least a user has to configure one of these him- or herself.
We have a couple of switches on the firewall options CGI already, so
I expect users to be confused where to find switches for DNS and for
firewall stuff, as this matter is something in between.
Thanks, and best regards,
Peter Müller
> Thank you everyone for this lively discussion.
>
> So I guess just blocking isn’t acceptable for everyone.
>
> What we could do instead is adding a checkbox to the new DNS settings section and call it “Enforce using IPFire as DNS resolver”.
>
> That could then activate the following:
>
> * Filter the domain name that Firefox uses to auto-enable DoH (*)
>
> * Reject any client connecting to any other DNS server on the internet
>
> Then, the only way to get DNS is to use the IPFire resolver. How is that?
>
> -Michael
>
> (*) I have absolutely no idea what they were thinking to entirely throw DHCP out of the window and decide that they can configure clients. That is an absolute no go. I think Mozilla opened a very very bad can of worms here and there is no chance to put the lid back on. I find this absolutely ridiculous what we are considering doing, but Mozilla clearly had other priorities. I do get the idea of it, that everyone has access to a free internet, but that is already the case on my network. I have a DNS resolver that does things for me that I want, and they are simply breaking common practise here. And that not even for all users, but only for a random selection. And on top of all of this they partnered up with Cloudflare after self-hosting everything for privacy reasons for years. Absolute bollocks.
>
next prev parent reply other threads:[~2020-03-03 18:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 11:47 Michael Tremer
2020-03-03 12:55 ` Aw: " Bernhard Bitsch
2020-03-03 13:15 ` Tapani Tarvainen
2020-03-03 13:58 ` Aw: " Bernhard Bitsch
2020-03-03 15:55 ` Tapani Tarvainen
2020-03-03 15:59 ` Arne Fitzenreiter
2020-03-03 16:06 ` Aw: Re: " Bernhard Bitsch
2020-03-03 17:18 ` Michael Tremer
2020-03-03 18:32 ` Peter Müller [this message]
2020-03-04 6:00 ` Tapani Tarvainen
2020-03-04 10:11 ` Michael Tremer
2020-03-04 10:56 ` Tapani Tarvainen
2020-03-04 10:58 ` Michael Tremer
2020-03-04 5:53 ` Tapani Tarvainen
2020-03-03 16:06 ` Arne Fitzenreiter
2020-03-03 14:09 ` Sorin-Mihai Vârgolici
2020-03-03 15:28 ` Peter Müller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1d0ca483-76bf-9588-a836-4344e5c14342@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox