IETF Logo Mail Archive

Re: [ietf-smtp] Public Key Look Up

Dave Crocker <dhc@dcrocker.net> Wed, 12 May 2021 16:46 UTC

Return-Path: <dhc@dcrocker.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 895E13A1043 for <ietf-smtp@ietfa.amsl.com>; Wed, 12 May 2021 09:46:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level:
X-Spam-Status: No, score=-2.101 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, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=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=dcrocker.net
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 z08B_V-Yj36f for <ietf-smtp@ietfa.amsl.com>; Wed, 12 May 2021 09:46:21 -0700 (PDT)
Received: from butterfly.birch.relay.mailchannels.net (butterfly.birch.relay.mailchannels.net [23.83.209.27]) (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 566FB3A1042 for <ietf-smtp@ietf.org>; Wed, 12 May 2021 09:46:20 -0700 (PDT)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id A991A7811A2; Wed, 12 May 2021 16:46:18 +0000 (UTC)
Received: from nl-srv-smtpout1.hostinger.io (100-96-133-96.trex.outbound.svc.cluster.local [100.96.133.96]) (Authenticated sender: hostingeremail) by relay.mailchannels.net (Postfix) with ESMTPA id C62DA781FFA; Wed, 12 May 2021 16:46:16 +0000 (UTC)
X-Sender-Id: hostingeremail|x-authsender|dhc@dcrocker.net
Received: from nl-srv-smtpout1.hostinger.io ([UNAVAILABLE]. [185.224.136.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256) by 100.96.133.96 (trex/6.2.1); Wed, 12 May 2021 16:46:18 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: hostingeremail|x-authsender|dhc@dcrocker.net
X-MailChannels-Auth-Id: hostingeremail
X-Soft-Print: 12867a7b1229a8c1_1620837978290_2386742993
X-MC-Loop-Signature: 1620837978290:793228227
X-MC-Ingress-Time: 1620837978289
Received: from [192.168.0.111] (c-24-130-56-204.hsd1.ca.comcast.net [24.130.56.204]) (Authenticated sender: dhc@dcrocker.net) by nl-srv-smtpout1.hostinger.io (smtp.hostinger.com) with ESMTPSA id 11CD7204F9D6; Wed, 12 May 2021 16:46:09 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=hostingermail-a; t=1620837975; bh=YKviPKiWdB6/w4dkm1kc1y2dVPr5WZ7f/wMIcbm3Ngo=; h=Reply-To:Subject:To:Cc:References:From:Date:In-Reply-To; b=NC3+ih9QD9wieM82TsfYrmaxbHkvtzWLRGZYb/e5OHlgCQK4Td0jbnYgarA7Mvg0t TlJ1QZOYqga7yC//1IP1wCX0kC7mV9hAgvAqZlfs2g9XncPwPmaTYbYhNmsmAszatS uo/rowLC9LYClN3Hd9ihnJaeHSrF0FmIKPtD5u//v1GtutP6thvjA36BSrtldHBHN/ FC3RQw8aoXEsBMe1EM68oy5bH1ac6JxyUfAx4qNirsNQg14zJGk2euXm0yH99QpMv0 k6ORkw94InymZSAxc3siBaFPr6KvOQ2vtsmIy17I1F/NpGocmMV4/Hn98gbSoUz360 EOVn5K4iAK4bg==
Reply-To: dcrocker@bbiw.net
To: Valdis Klētnieks <valdis.kletnieks@vt.edu>, Alessandro Vesely <vesely@tana.it>
Cc: John C Klensin <john-ietf@jck.com>, John Levine <johnl@taugh.com>, ietf-smtp@ietf.org
References: <20210511185543.C751179052B@ary.qy> <D7EABCF7E8976BE735927C69@PSB> <79ed2289-80af-5744-86f1-6d7a13b730ab@tana.it> <676285.1620837061@turing-police>
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <b523cf8a-d57c-593e-ffe6-07cb794f82e2@dcrocker.net>
Date: Wed, 12 May 2021 09:46:08 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1
MIME-Version: 1.0
In-Reply-To: <676285.1620837061@turing-police>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/79uDa6MJwnjiYHbZTrr7JQBLRLk>
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: Wed, 12 May 2021 16:46:27 -0000

On 5/12/2021 9:31 AM, Valdis Klētnieks wrote:
> Right.  Your MX publishes a public key to which it has the corresponding
> private key.  This is well understood technology - see any company that
> intercepts https:// and re-encrypts the user-side traffic using their own keys.

or DKIM.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email