IETF Logo Mail Archive

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

Hector Santos <hsantos@isdg.net> Wed, 16 October 2019 01:37 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 1DF2E120843 for <ietf-smtp@ietfa.amsl.com>; Tue, 15 Oct 2019 18:37:11 -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=ABaFWVDW; dkim=pass (1024-bit key) header.d=beta.winserver.com header.b=AuAePd06
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 p3wBLKi6uoev for <ietf-smtp@ietfa.amsl.com>; Tue, 15 Oct 2019 18:37:09 -0700 (PDT)
Received: from mail.winserver.com (secure.winserver.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 33C13120830 for <ietf-smtp@ietf.org>; Tue, 15 Oct 2019 18:37:08 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1033; t=1571189822; atps=ietf.org; atpsh=sha1; h=Received:Received:Received:Received:Message-ID:Date:From: Organization:To:Subject:List-ID; bh=b0Ta2q/oPrU6JWffKrVijwBQN+M=; b=ABaFWVDWIWNqJSUjWS9CBWu/KmvG4TszZ3R1l0T4G+J/DD57rQwEbgaHvx1IUI 0HHJhZ9pUVbrSN54jjAAJhJSzbHN9HMIrlFzCSfhlzzx4hHbl2hN0vYtlbhbCf5v +wlpS9tFfq/aYDkMgP9M/D5/WngjsnNrXnSdVYi9WCeS0=
Received: by winserver.com (Wildcat! SMTP Router v8.0.454.9) for ietf-smtp@ietf.org; Tue, 15 Oct 2019 21:37:02 -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 3392202433.1.6068; Tue, 15 Oct 2019 21:37:02 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1033; t=1571189756; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=XOmVRjf 64yWLdc0gYbVANZBBC0scJE5Qs0bs/jIQmWs=; b=AuAePd06FuplMwEohee+eXB SzS1umI/XiBsZY5rwzP6cbTe1m+MWomD+B4XPKAM+iPPDGXehyIwFv46MMOmF/Mr Arsbfr7EsmZoxYMqSw1azK+mWFqzfACmAy8egOwlx+471Fn4iLO2w+nUCQDQ4puB krxxGMXAqHMfUZNfhExo=
Received: by beta.winserver.com (Wildcat! SMTP Router v8.0.454.9) for ietf-smtp@ietf.org; Tue, 15 Oct 2019 21:35:56 -0400
Received: from [192.168.1.68] ([75.26.216.248]) by beta.winserver.com (Wildcat! SMTP v8.0.454.9) with ESMTP id 1071012907.44280.10084; Tue, 15 Oct 2019 21:35:55 -0400
Message-ID: <5DA6743B.5070202@isdg.net>
Date: Tue, 15 Oct 2019 21:36:59 -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: 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>
In-Reply-To: <96055.1571170998@turing-police>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/4AVSYiOZwIqS2L7huxmuzJ_vksQ>
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 01:37:11 -0000

On 10/15/2019 4:23 PM, Valdis Klētnieks wrote:
> On Tue, 15 Oct 2019 12:52:18 -0400, Hector Santos said:
>
>> But it just dawn on me, should a site like the above domain be trusted
>> as a TTP (Trusted Third Party) CA?  The bundle can contain TTP
>> "posers."   For that matter, why should the user trust any CA anyway?
>
> If there were a small number of top-level CAs of irreproachable reputation,
> it wold be one thing. But when the bar is low enough that there's 600+
> organizations that qualify....

The old centralization vs decentralization dilemma.

The technical security aspect of encryption is no longer good enough 
-- certs now have to be CA-signed now.   What concerns me is when 
self-signed certs will be technically degraded (for many reasons, 
including DPI overhead).  I am seeing it at a localized (HTTPS) level. 
I predict this is going to be a big problem.  For SMTP, we don't have 
the same Browser/CA market control.

Thanks Valdis and Arnt.

P.S.  What is the end result of all this?

-- 
HLS

v2.23.0 | Report a Bug | By Email