Re: Q: Automatic, secure proxy selection

Paul Vixie <> Mon, 20 July 2020 07:45 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B5B7B3A081F for <>; Mon, 20 Jul 2020 00:45:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.92
X-Spam-Status: No, score=-2.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id KweN2Q6491lf for <>; Mon, 20 Jul 2020 00:45:01 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6CB583A0815 for <>; Mon, 20 Jul 2020 00:45:01 -0700 (PDT)
Received: from lists by with local (Exim 4.92) (envelope-from <>) id 1jxQTe-00060p-Er for; Mon, 20 Jul 2020 07:44:46 +0000
Resent-Date: Mon, 20 Jul 2020 07:44:46 +0000
Resent-Message-Id: <>
Received: from ([]) by with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <>) id 1jxQTd-000603-9v for; Mon, 20 Jul 2020 07:44:45 +0000
Received: from [2001:559:8000:cd::5] ( by with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <>) id 1jxQTZ-00008a-7c for; Mon, 20 Jul 2020 07:44:43 +0000
Received: from linux-9daj.localnet ( []) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (1024 bits) server-digest SHA256) (Client did not present a certificate) by (Postfix) with ESMTPSA id C34CDC3F16; Mon, 20 Jul 2020 07:44:27 +0000 (UTC)
From: Paul Vixie <>
To: Toerless Eckert <>,
Cc:, Mark Nottingham <>
Date: Mon, 20 Jul 2020 07:44:26 +0000
Message-ID: <1737874.0qUVdPgL38@linux-9daj>
Organization: none
In-Reply-To: <>
References: <> <>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Received-SPF: pass client-ip=2001:559:8000:cd::5;;
X-W3C-Hub-Spam-Status: No, score=-3.1
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: 1jxQTZ-00008a-7c 20890886ee9203b48371c3a10dea14f1
Subject: Re: Q: Automatic, secure proxy selection
Archived-At: <>
X-Mailing-List: <> archive/latest/37889
Precedence: list
List-Id: <>
List-Help: <>
List-Post: <>
List-Unsubscribe: <>

On Monday, 20 July 2020 07:02:14 UTC Mark Nottingham wrote:
> This question is likely better asked on the DoH or another list, as it's not
> specific to HTTP.

mine is. since dhcp is not secure, and since i won't permit any device on my 
home or corporate network to call its external mothership using crypto, i 
operate a proxy which devices on my home or corporate network must trust and 
must use. no exceptions.

how am i expected to tell alexa, siri, hey, chromecast, and the rest of the 
embedded devices my family and employees want to use, that they have to use a 
proxy if they want to reach the outside world?

this isn't DoH specific, though DoH as an HTTP use case is affected by it.

the user-centric / app-centric network model assumes that all on-path 
attackers are oppositional, like evil ISP's or authoritarian governments. i'm 
neither, i'm just a head of household and a CEO, and i will be held 
responsible for whatever traffic my network emits, and i want to exercise that 
responsibility wisely.

toerless's question resonated with me.