Re: [ietf-smtp] [OT] (signed TLDs)

Hector Santos <hsantos@isdg.net> Wed, 16 October 2019 03:30 UTC

Return-Path: <hsantos@isdg.net>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99C69120849 for <ietf-smtp@ietfa.amsl.com>; Tue, 15 Oct 2019 20:30:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isdg.net header.b=P83CxfyC; dkim=pass (1024-bit key) header.d=beta.winserver.com header.b=lG8uJytx
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dgGGzJS7zrVk for <ietf-smtp@ietfa.amsl.com>; Tue, 15 Oct 2019 20:30:39 -0700 (PDT)
Received: from mail.winserver.com (mail.santronics.com [76.245.57.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 736BE120848 for <ietf-smtp@ietf.org>; Tue, 15 Oct 2019 20:30:39 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=702; t=1571196638; atps=ietf.org; atpsh=sha1; h=Received:Received:Received:Received:Message-ID:Date:From: Organization:To:Subject:List-ID; bh=yKsMBWATiupO83ATeFXvxH+oUUc=; b=P83CxfyC2Rhh/zK92gE/VqlPAdxpX88yjmB8U5++iTZAa16utQJYplWNMCxMZB NeCNnN5MOAcNey9Psyk1MI7tU3wEtvAgV5sxriwDkhNopfc7IXnbq8eFIZz5vN3r NPZ+lZ56aI3WlQMMsmMhzPmg3VJynISkxeItKjXszrcfE=
Received: by winserver.com (Wildcat! SMTP Router v8.0.454.9) for ietf-smtp@ietf.org; Tue, 15 Oct 2019 23:30:38 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;
Received: from beta.winserver.com ([76.245.57.74]) by winserver.com (Wildcat! SMTP v8.0.454.9) with ESMTP id 3399017664.1.5524; Tue, 15 Oct 2019 23:30:37 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=702; t=1571196574; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=aiOhv6k VPN35cMrZGusBsgTDwYdvzQrscEvQVOuVH2U=; b=lG8uJytx7PX/IOkkPsoHUV/ CbqxCOx/ZTXnxzDxK3PAaoie7h5qd7T8UbsEd6Zwv6i+V4xzCoB3HpRlX97XP2dC +GSpCALAAFSRqFdhDIbUm9AcN5D6sw9l93CwxnyRGYo9xn2zlWRiBKWulsGJ8bsT MOGeBUwIA13kONVtceQM=
Received: by beta.winserver.com (Wildcat! SMTP Router v8.0.454.9) for ietf-smtp@ietf.org; Tue, 15 Oct 2019 23:29:34 -0400
Received: from [192.168.1.68] ([75.26.216.248]) by beta.winserver.com (Wildcat! SMTP v8.0.454.9) with ESMTP id 1077831329.44280.8044; Tue, 15 Oct 2019 23:29:33 -0400
Message-ID: <5DA68EDE.1010201@isdg.net>
Date: Tue, 15 Oct 2019 23:30:38 -0400
From: Hector Santos <hsantos@isdg.net>
Reply-To: hsantos@isdg.net
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.8.1
MIME-Version: 1.0
To: SMTP Interest Group <ietf-smtp@ietf.org>
References: <20191011160802.50C81C9B780@ary.qy> <alpine.DEB.2.20.1910141200120.8949@grey.csi.cam.ac.uk> <alpine.OSX.2.21.99999.368.1910141020460.72467@ary.local> <alpine.DEB.2.20.1910151228410.8949@grey.csi.cam.ac.uk> <5DA5F942.5030307@isdg.net> <96055.1571170998@turing-police> <5DA6743B.5070202@isdg.net> <0ab60cd9-759a-572a-622f-41c841e69350@network-heretics.com>
In-Reply-To: <0ab60cd9-759a-572a-622f-41c841e69350@network-heretics.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/bYClGL53Fpht_r5mO1s-vnkLX0s>
Subject: Re: [ietf-smtp] [OT] (signed TLDs)
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Oct 2019 03:30:42 -0000

On 10/15/2019 9:56 PM, Keith Moore wrote:
> On 10/15/19 9:36 PM, Hector Santos wrote:
>
>> The technical security aspect of encryption is no longer good enough
>> -- certs now have to be CA-signed now.
>
> Certs that weren't signed by a trusted party were never worth anything
> anyway, unless maybe you manually pinned them.
>
> Keith

Yes, 100% +1 but traditionally, it is a known target, i.e. well known 
users using a well-known trusted site. As long as the common name 
matches, it is secured. No?
What I am seeing for the first time ever in HTTP history, HTTP comm 
I/O is ok, HTTPS is degraded by the ISP if self-signed. Explain that. 
  They can't. Too classified. :-(


-- 
HLS