Re: [ietf-smtp] Public Key Look Up

John Levine <johnl@taugh.com> Sat, 08 May 2021 17:26 UTC

Return-Path: <johnl@iecc.com>
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 2629C3A064A for <ietf-smtp@ietfa.amsl.com>; Sat, 8 May 2021 10:26:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level:
X-Spam-Status: No, score=-1.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=TxaESIpP; dkim=pass (2048-bit key) header.d=taugh.com header.b=JJqxI7Ld
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 TzWdgUT6iPgR for <ietf-smtp@ietfa.amsl.com>; Sat, 8 May 2021 10:26:05 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 19D7A3A0603 for <ietf-smtp@ietf.org>; Sat, 8 May 2021 10:26:04 -0700 (PDT)
Received: (qmail 64072 invoked from network); 8 May 2021 17:26:03 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=fa46.6096c9ab.k2105; bh=PahHN9ekVSCYT9yYzgW81XxV9NLnC3ZmvlbLoF/BFIA=; b=TxaESIpPwOrpz7raAbbB7ytXsJQ0axaMnXloC8m55LWbPVsXEj3WD1mIUGTo65fzy3dHm5rsBtnBB7Appg41NkGcRZ8/qeVXkPcN+8I55VF9MoVc8v53gM0uoMEXIh2k4kUIaVVQblXC3KlNml6rGT9NzNCdt2mtf4zo8QomAqnRnlkfIfP1rsm8OgT/Qnf3P0WOPHX3+drdXwAUtefKhQHF+8Sfz4MziAzgXfjGH0wI7n+b8fEDGcAKByW9MgCORWjNQCLPhtRmuk7zlbU7jACA/wICtBByqmEufIEEYYev4CfL7XL1AJWbXzyntkXuhFMx91RokboLLpW49jftqg==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:cleverness; s=fa46.6096c9ab.k2105; bh=PahHN9ekVSCYT9yYzgW81XxV9NLnC3ZmvlbLoF/BFIA=; b=JJqxI7LdlxHPgYCC/VLYdgyJcsThk2HkdGRCyNMofZfwp2Rvq6vE5u0ZsnOo+VHs0riI3Ta+nJtetjobf8B28T/LxQxXlx0pdSuk1d272GWkQ9VJ8VnXxgjx33Vj8sZJSdL/yg8sXKa6uDvzKNkNAmK8YsvNGQNVfo2664qyOwPA8JGIO0TSTXGbZX0eGoRvmZ0UMocYkA/VXyIagcSP+mpaxt/fMwvQ66U5amrCCoER14G1lI/KT6CAJvQ3n2l9ON6uZ9BuVZoC9+KVsssQVgGzwCnn32SKKw7n6TRtxzblPk5kksr6rq0CkDO/fbZtWX24ZPwr9MkBPk1AcfV1Sg==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 08 May 2021 17:26:03 -0000
Received: by ary.qy (Postfix, from userid 501) id CC09D72BE50; Sat, 8 May 2021 13:26:02 -0400 (EDT)
Date: Sat, 08 May 2021 13:26:02 -0400
Message-Id: <20210508172602.CC09D72BE50@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
Cc: john-ietf@jck.com
In-Reply-To: <2A1D13B4D5EFA6CA70790D60@PSB>
Organization: Taughannock Networks
X-Headerized: yes
Cleverness: minimal
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/9JpU2DBMyz4XiJDE1gnU5GMESyA>
Subject: Re: [ietf-smtp] Public Key Look Up
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: Sat, 08 May 2021 17:26:11 -0000

It appears that John C Klensin  <john-ietf@jck.com> said:
>FWIW, also note that ideas of putting user or mailbox names (not
>just host names) into the DNS to support a variety of things has
>been around since the early design of the DNS.

I'd forgotten about RFC 7929 which purports to put PGP keys
in the DNS.  It's fairly badly broken since mail and the DNS
have different ideas about name matching, but it doesn't matter
because nobody ever has used it.

>I want to stress that I don't think this is a terrible idea,
>especially if it were used to retrieve keys for S/MIME or PGP
>use rather than inventing yet another mechanism.

I think it's a terrible idea both because it puts the keys in the wrong
place and the reasons you gave, extensions are optional which means
not implemented.

>At least for PGP, there are widely available public key stores
>from which an interested MUA could easily retrieve any keys that
>happen to be there using LDAP and probably other mechanisms --
>all less complicated than building something into SMTP. ...

Right.  This idea has failed plenty of times already.

R's,
John