From: Bernhard Bitsch <Bernhard.Bitsch@gmx.de>
To: development@lists.ipfire.org
Subject: Aw: Should we block DoH by default?
Date: Tue, 03 Mar 2020 13:55:22 +0100 [thread overview]
Message-ID: <trinity-c376d19e-d1d8-43c8-9f5b-be9ea9dce4fb-1583240122792@3c-app-gmx-bap45> (raw)
In-Reply-To: <83D08EF2-A2BC-4759-9F69-E42BADBDA3C9@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
Hi,
> Gesendet: Dienstag, 03. März 2020 um 12:47 Uhr
> Von: "Michael Tremer" <michael.tremer(a)ipfire.org>
> An: "IPFire: Development-List" <development(a)lists.ipfire.org>
> Betreff: Should we block DoH by default?
>
> Hello,
>
> A post on the community portal has raised my attention today:
>
> https://community.ipfire.org/t/firefox-doh-and-ipfire-blocked-dns-ports/1466/3
>
> The author links an article that explains how Firefox decides to enable DoH.
>
> I do not want DoH. I do not like it. Mozilla is doing something really really bad here.
>
> We could consider always blocking this domain and always return NXDOMAIN or something else that falls into the “negative” category.
>
> That way we can guarantee (at least for now) that Firefox users will still use the IPFire resolver.
>
> Would anybody be against this?
>
No, on the contrary.
If we build with much effort an evironment, that does DNS secoure and with minimal overhead in "spying" ( see the excellent blog article by Michael ), DoH would be contraproductive.
- Bernhard
> -Michael
next prev parent reply other threads:[~2020-03-03 12:55 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 ` Bernhard Bitsch [this message]
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
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=trinity-c376d19e-d1d8-43c8-9f5b-be9ea9dce4fb-1583240122792@3c-app-gmx-bap45 \
--to=bernhard.bitsch@gmx.de \
--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