Re: [ietf-smtp] Public Key Look Up

Alessandro Vesely <vesely@tana.it> Thu, 13 May 2021 07:20 UTC

Return-Path: <vesely@tana.it>
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 776D93A2D16 for <ietf-smtp@ietfa.amsl.com>; Thu, 13 May 2021 00:20:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1152-bit key) header.d=tana.it
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 tDdOjnoVhXYZ for <ietf-smtp@ietfa.amsl.com>; Thu, 13 May 2021 00:20:13 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) (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 821763A2D15 for <ietf-smtp@ietf.org>; Thu, 13 May 2021 00:20:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=delta; t=1620890410; bh=+okvzIod4MEM5VjMKwgxutCaPgvtRh761HNKaObeMKs=; l=770; h=To:References:From:Date:In-Reply-To; b=B7QyVYufktWORiaPjl1zxzkySF/D38zzzTynJoFmbgnPFdIS2R0gYkVRoB0rcXrma dMMNLhNePo4GYUrjhIPOelr7pgBpS02cwrKV/N/qXeVHDh9iWmO+hwgLFpV/Vt+CqK IaIJiYjbNGKZHeXcKlExWs6LKpW9AnNj7JEdOkrotstABAu0OhUapdsQfwWlK
Authentication-Results: tana.it; auth=pass (details omitted)
Original-From: Alessandro Vesely <vesely@tana.it>
Received: from [172.25.197.111] (pcale.tana [172.25.197.111]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k, TLS: TLS1.3, 128bits, ECDHE_RSA_AES_128_GCM_SHA256) by wmail.tana.it with ESMTPSA id 00000000005DC0D6.00000000609CD32A.000039FD; Thu, 13 May 2021 09:20:10 +0200
To: dcrocker@bbiw.net, ietf-smtp@ietf.org
References: <20210511185543.C751179052B@ary.qy> <D7EABCF7E8976BE735927C69@PSB> <79ed2289-80af-5744-86f1-6d7a13b730ab@tana.it> <676285.1620837061@turing-police> <b523cf8a-d57c-593e-ffe6-07cb794f82e2@dcrocker.net> <a0d3aecc-d36e-3a16-3bdc-7ca6f2bca5c0@tana.it> <5a22f7bf-8e92-21e9-f86b-7a624014c91c@dcrocker.net>
From: Alessandro Vesely <vesely@tana.it>
Message-ID: <2ab882c0-35e8-9098-bd02-48cf1cb314fb@tana.it>
Date: Thu, 13 May 2021 09:20:09 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.9.0
MIME-Version: 1.0
In-Reply-To: <5a22f7bf-8e92-21e9-f86b-7a624014c91c@dcrocker.net>
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/LYGGdh_wQgrATSt6S4m5XBTXEW0>
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: Thu, 13 May 2021 07:20:19 -0000

On Wed 12/May/2021 20:44:34 +0200 Dave Crocker wrote:
> On 5/12/2021 9:57 AM, Alessandro Vesely wrote:
>>
>> Neither case provides for end-to-end crypto.  (Hm... possibly except DKIM for 
>> postmaster to postmaster communication, deploying the binary key as OpenGPG.  
>> Not an alluring technique.)
> 
> DKIM doesn't use encryption, but it does do signing, which is a crypto function.
> 
> More simply: the thing that is published in a DKIM record is a public key.


Right.  Anyway, if I encrypted something using your DKIM public key, you could 
easily decrypt it using the private key.  (There's a script by the Monkeysphere 
Project, pem2openpgp, which can transform a DKIM private key into an OpenPGP 
key for signing.  A silly exercise.)


Best
Ale
--