Re: [ietf-smtp] Public Key Look Up

Richard Clayton <richard@highwayman.com> Thu, 13 May 2021 09:34 UTC

Return-Path: <richard@highwayman.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 3DA3D3A315D for <ietf-smtp@ietfa.amsl.com>; Thu, 13 May 2021 02:34:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 GzpJyLmTkDiz for <ietf-smtp@ietfa.amsl.com>; Thu, 13 May 2021 02:34:20 -0700 (PDT)
Received: from mail.highwayman.com (mail.highwayman.com [82.69.6.249]) (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 C29CE3A3158 for <ietf-smtp@ietf.org>; Thu, 13 May 2021 02:34:20 -0700 (PDT)
Received: from localhost ([127.0.0.1]:52502 helo=happyday.al.cl.cam.ac.uk) by mail.highwayman.com with esmtp (Exim 4.94.2) (envelope-from <richard@highwayman.com>) id 1lh7jU-000JJq-RW for ietf-smtp@ietf.org; Thu, 13 May 2021 09:34:16 +0000
Message-ID: <g5JroVBVJPngFAlS@highwayman.com>
Date: Thu, 13 May 2021 10:33:09 +0100
To: ietf-smtp@ietf.org
From: Richard Clayton <richard@highwayman.com>
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> <2ab882c0-35e8-9098-bd02-48cf1cb314fb@tana.it>
In-Reply-To: <2ab882c0-35e8-9098-bd02-48cf1cb314fb@tana.it>
MIME-Version: 1.0
X-Mailer: Turnpike Integrated Version 5.03 M <Ti9$+f9b77fPDPKLdaR+deFnQb>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/h26zrXCTTFucX38RgdVM0oUcvCw>
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 09:34:25 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In message <2ab882c0-35e8-9098-bd02-48cf1cb314fb@tana.it>, Alessandro
Vesely <vesely@tana.it> writes

>Right.  Anyway, if I encrypted something using your DKIM public key, you could 
>easily decrypt it using the private key.

please don't do that -- from a legal standpoint when resisting attempts
by Law Enforcement to request private keys, it puts you on very strong
ground to argue that a key has only ever been used for authentication
rather than encryption

also, by using the same key for different purposes you increase the risk
of chosen protocol attacks and other bad things happening, which is why
expert advice is to always to avoid loading the gun, even if you are
promising never to point it anywhere near your lower extremities

- -- 
richard                                                   Richard Clayton

Those who would give up essential Liberty, to purchase a little temporary 
Safety, deserve neither Liberty nor Safety. Benjamin Franklin 11 Nov 1755

-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.7.1

iQA/AwUBYJzyVd2nQQHFxEViEQLitwCfcZ3a2VwCSDavft0RZT/23GQoMBYAn1+D
dXzhuvda4SxzC5YZ+7PZBcrI
=wRnf
-----END PGP SIGNATURE-----