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 12:56:45 +0200	[thread overview]
Message-ID: <20200304105645.GA18957@tehanu.it.jyu.fi> (raw)
In-Reply-To: <4E2571B2-5250-42CD-B608-0353D579E088@ipfire.org>

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

On Mar 04 10:11, Michael Tremer (michael.tremer(a)ipfire.org) wrote:

> >> 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?
> 
> Yes, we could do that for 53 UDP and TCP, but not for 853 obviously.

Right. But if some IoT thingy relies on a hard-coded DNS-over-TLS
server there's little we can do about it, but redirection could
save the day with those that use good old 53.

-- 
Tapani Tarvainen

  reply	other threads:[~2020-03-04 10:56 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
2020-03-04 10:11               ` Michael Tremer
2020-03-04 10:56                 ` Tapani Tarvainen [this message]
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=20200304105645.GA18957@tehanu.it.jyu.fi \
    --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