public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Tapani Tarvainen <ipfire@tapanitarvainen.fi>
To: development@lists.ipfire.org
Subject: Re: Should we block DoH by default?
Date: Wed, 04 Mar 2020 08:00:02 +0200	[thread overview]
Message-ID: <20200304060002.GC26106@tarvainen.info> (raw)
In-Reply-To: <1d0ca483-76bf-9588-a836-4344e5c14342@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 696 bytes --]

On Tue, Mar 03, 2020 at 06:32:00PM +0000, Peter Müller (peter.mueller(a)ipfire.org) wrote:

> 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.

Thinking about those, how about an option to *redirect* connections
to port 53 of external servers to IPFire rather than rejecting them?

-- 
Tapani Tarvainen

  reply	other threads:[~2020-03-04  6:00 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
2020-03-04  6:00             ` Tapani Tarvainen [this message]
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=20200304060002.GC26106@tarvainen.info \
    --to=ipfire@tapanitarvainen.fi \
    --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