Re: [Ietf-dkim] Testing a DKIM implementation

Steffen Nurpmeso <steffen@sdaoden.eu> Sat, 23 March 2024 21:53 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 36EAAC14F5EC for <ietf-dkim@ietfa.amsl.com>; Sat, 23 Mar 2024 14:53:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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="GBasmHQZ"; dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=sdaoden.eu header.b="0m2NRsxd"
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 CrDjWy8Dy8VK for <ietf-dkim@ietfa.amsl.com>; Sat, 23 Mar 2024 14:53:34 -0700 (PDT)
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) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BA8FC14F6FC for <ietf-dkim@ietf.org>; Sat, 23 Mar 2024 14:53:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sdaoden.eu; s=citron; t=1711230810; x=1711897476; h=date:author:from:to:cc:subject: message-id:in-reply-to:references:mail-followup-to:openpgp:blahblahblah: mime-version:content-type:content-transfer-encoding:author:from:subject: date:to:cc:resent-date:resent-from:resent-to:resent-cc:in-reply-to: references:mime-version:content-type:content-transfer-encoding:message-id: mail-followup-to:openpgp:blahblahblah; bh=6vuVkKb7yqncoqEZL6prya2w5kgzFhiaMLMKcfnTToA=; b=GBasmHQZkTXAmIQK+0os4LVahvRRe8sCcokOz8Prn61U7Vi+xkJkEYxHk1dqwkr+51p7x0GC 68RJ3mLwIQZM9X2OETXpDaa/qMg/4LwFRu5PteMhNtveXRzgVyU3G89usHDOWnrNLe5jDgtD8w b4H1WfmZuloK41ljrd1E+3SOBNo2ebAwKvsoWmkivJSFJ4CLkV+0B6c//PoGejopuWMEVkUtu3 yGnooGkwqGHUOcJLLK6gEreIOKAmCrF8DVdLybTSFppN9fcEYfPqsD4XQrCKDxkf8MYgPgxcVt wHjllZSTgeVljwi/f/ROJ7OwKNgPAzYgxPHml/8dpfu6qelA==
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=sdaoden.eu; s=orange; t=1711230810; x=1711897476; h=date:author:from:to:cc:subject: message-id:in-reply-to:references:mail-followup-to:openpgp:blahblahblah: mime-version:content-type:content-transfer-encoding:author:from:subject: date:to:cc:resent-date:resent-from:resent-to:resent-cc:in-reply-to: references:mime-version:content-type:content-transfer-encoding:message-id: mail-followup-to:openpgp:blahblahblah; bh=6vuVkKb7yqncoqEZL6prya2w5kgzFhiaMLMKcfnTToA=; b=0m2NRsxdOtSNVjWqT0BkTbEMSzsbVOwqqK0W113znJXJlj5qVvUHYufb+mkoT5MkXO0J5W70 q4iXpoTcmaWdCA==
Date: Sat, 23 Mar 2024 21:41:52 +0100
Author: Steffen Nurpmeso <steffen@sdaoden.eu>
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: Matthäus Wander <mail=40wander.science@dmarc.ietf.org>
Cc: ietf-dkim@ietf.org
Message-ID: <20240323204152.zti8hTas@steffen%sdaoden.eu>
In-Reply-To: <25cebd13-10a2-4b56-887a-f5bcaf0e0d46@wander.science>
References: <65FD789C.26406.50826198@David.Harris.pmail.gen.nz> <25cebd13-10a2-4b56-887a-f5bcaf0e0d46@wander.science>
Mail-Followup-To: Matthäus Wander <mail=40wander.science@dmarc.ietf.org>, ietf-dkim@ietf.org
User-Agent: s-nail v14.9.24-612-g7e3bfac540
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.
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-dkim/xfu3qzgLe9Wm27iDF_HcUT9c9YY>
Subject: Re: [Ietf-dkim] Testing a DKIM implementation
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: Sat, 23 Mar 2024 21:53:40 -0000

Matthäus Wander wrote in
 <25cebd13-10a2-4b56-887a-f5bcaf0e0d46@wander.science>:
 |David Harris wrote on 2024-03-22 13:25:
 |> I now have my implementation complete: I was wondering if there is a
 |> recommended way of testing it - for instance, a reference site that \
 |> allows you
 |> to send messages and then replies with information about the correctness \
 |> of
 |> your implementation, or an application that can generate signatures \
 |> for data
 |> you supply, showing its work product (the various hashes and canonicaliz\
 |> ed
 |> forms) so you can compare it with your own.
 |
 |Maybe this one helps:
 |https://wander.science/projects/email/dkimtest/
 |
 |Ed25519 is supported.

Thanks for this!  Unfortunately i did not discover it earlier.
I mean, i had dkimpy (and dkimpy-milter) here, but it wants
a fully blown setup and installation, ie: access to DNS and all
that, the entire python3 infrastructure.
(When i extend my -sign for full operation somewhen in autumn
i hope i can somehow implement a test mode where the public (DNS)
keys can be fed in via some option.)

--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)