IETF Logo Mail Archive

Re: [Ietf-dkim] Fwd: Re: [..] Recommendation for dkim signing

Steffen Nurpmeso <steffen@sdaoden.eu> Wed, 06 March 2024 23:05 UTC

Return-Path: <steffen@sdaoden.eu>
X-Original-To: ietf-dkim@ietfa.amsl.com
Delivered-To: ietf-dkim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC7B7C14F6A3 for <ietf-dkim@ietfa.amsl.com>; Wed, 6 Mar 2024 15:05:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sdaoden.eu header.b="QFZdoBMp"; dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=sdaoden.eu header.b="9JLDh7Fw"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4ZoqrZKMzfe6 for <ietf-dkim@ietfa.amsl.com>; Wed, 6 Mar 2024 15:05:28 -0800 (PST)
Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C3A2C14F69C for <ietf-dkim@ietf.org>; Wed, 6 Mar 2024 15:05:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sdaoden.eu; s=citron; t=1709766327; h=date:author:from:to:cc:subject:message-id: in-reply-to:references:author:from:subject:date:to:cc:in-reply-to: references:message-id; bh=JLQ4BArr4OSRcasHhl2+UMezqwu6vw/aIBUAPPurKAQ=; b=QFZdoBMpoq+74rm7jdCVCLQT4/JdFQoRS6YZUlQP0WGj67Vbh6oB5ihisfu5wSWVt1Hi/TpV bW4CINmPsvQ+SSlsFkXPRrES4US4C/Wf8iln70H2Hnuinnq5YkANQMtLO2lOPGzqf4EljXUqE5 K40yWvyJESVH8B5rUDnvU0I6GEXuCwo5yCRVW4hqHbjLEfcHc+XwfTo2lgT0BxEB2UAicPRUzF 4uqSHv8eC8miuSOrU4lxkhCZdH7YvSk42qPlUWFfmMPIK23orvxQoIsOYC+HJaZls0DQ7xGDiw O+noqBGvRlsRTnKtcoV2Yk+vzn9CX3+cii13eOUzWWq/EHUA==
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=sdaoden.eu; s=orange; t=1709766327; h=date:author:from:to:cc:subject:message-id: in-reply-to:references:author:from:subject:date:to:cc:in-reply-to: references:message-id; bh=JLQ4BArr4OSRcasHhl2+UMezqwu6vw/aIBUAPPurKAQ=; b=9JLDh7FwhrMSatBhWobDYYEV5kXkgaUGwlyC9uuQoo5ZCXuCaGs+Z/0msEGkOZBjgt5gVBiw tu0Z/OEg943oAw==
Date: Thu, 07 Mar 2024 00:05:26 +0100
Author: Steffen Nurpmeso <steffen@sdaoden.eu>
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Scott Kitterman <ietf-dkim@kitterman.com>
Cc: ietf-dkim@ietf.org
Message-ID: <20240306230526.tcmkMKA1@steffen%sdaoden.eu>
In-Reply-To: <9EE553EC-AA5B-4DAC-BF4D-9A0FFB28911E@kitterman.com>
References: <20240306215650.uXHHYo2j@steffen%sdaoden.eu> <C9EF0654-C410-46DC-B9A7-716E3ECA0B4E@kitterman.com> <20240306224151.r4D7UEwr@steffen%sdaoden.eu> <9EE553EC-AA5B-4DAC-BF4D-9A0FFB28911E@kitterman.com>
Mail-Followup-To: Scott Kitterman <ietf-dkim@kitterman.com>, ietf-dkim@ietf.org
User-Agent: s-nail v14.9.24-608-gfa6c5c5231
OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt
BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs.
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/1u9sTj2MEHo46b7JOz3o2kKqMJQ>
Subject: Re: [Ietf-dkim] Fwd: Re: [..] Recommendation for dkim signing
X-BeenThere: ietf-dkim@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF DKIM List <ietf-dkim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-dkim>, <mailto:ietf-dkim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-dkim/>
List-Post: <mailto:ietf-dkim@ietf.org>
List-Help: <mailto:ietf-dkim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Mar 2024 23:05:33 -0000

Scott Kitterman wrote in
 <9EE553EC-AA5B-4DAC-BF4D-9A0FFB28911E@kitterman.com>:
 |On March 6, 2024 10:41:51 PM UTC, Steffen Nurpmeso <steffen@sdaoden.eu> \
 |wrote:
 |>Scott Kitterman wrote in
 |> <C9EF0654-C410-46DC-B9A7-716E3ECA0B4E@kitterman.com>:
 |>|On March 6, 2024 9:56:50 PM UTC, Steffen Nurpmeso <steffen@sdaoden.eu> \
 |>|wrote:
 ...
 |>|>So now that i have DKIM myself i tested.
 |>|>And *no* verification software i can reach actually supports
 |>|>Ed25519-sha256 as of RFC 8463 from September 2018!
 |>|
 |>|In addition to my dkimpy-milter, exam supports it and believe opendkim \
 |>
 |>Yes, you do support it.  I know of no endpoint i could reach out
 |>to test this, however.  But yes, of course your software
 |>thankfully supports it.
 ...
 |>exam i do not know, and OpenDKIM i am pretty sure does not support
 |>it, at least the Sourceforge.net thing; i have a local copy and
 |>the last change was in 2015.
 ...
 |For opendkim, you need to look on GitHub.  There has been some further \
 |development there.

Oh!  Hmm.  The difference seems niche i'd say.
Btw now that i look at that thanks to my configurable header
display in the console based MUA i use, you use Ed25519 first and
then RSA, forcefully breaking the incapable IETF DKIM checks and
Microsoft as a whole.  That is brave!
I follow (a bit) by re-enabling Ed!!

Ciao, and greetings from Germany!

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

v2.23.0 | Report a Bug | By Email