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: Re: Should we block DoH by default?
Date: Tue, 03 Mar 2020 17:55:17 +0200	[thread overview]
Message-ID: <20200303155517.GF31441@tehanu.it.jyu.fi> (raw)
In-Reply-To: <trinity-2fe2ee85-83a3-48d4-87ba-13b6f7b290d9-1583243900256@3c-app-gmx-bap45>

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

On Mar 03 14:58, Bernhard Bitsch (Bernhard.Bitsch(a)gmx.de) wrote:

> >  I don't want to be *forced* to use IpFire resolver.

To clarify: I, *AS A SYSADMIN*, don't want to be forced to do so.

> But one task of an internet appliance like IPFire is just to force
> such local rules.

That is different: again, as sysadmin I may want to enforce such
rules inside my net, one way or the other.

Perhaps I should also note that Firefox allows you to choose your own
DoH server, you don't have to use Mozilla or Cloudflare or whatever,
and at some point it might be good to have DoH server built into
IPFire.

-- 
Tapani Tarvainen

  reply	other threads:[~2020-03-03 15: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 ` 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 [this message]
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=20200303155517.GF31441@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