Re: [Ietf-dkim] RFC 8463: DNS textual form underspecified

Steffen Nurpmeso <steffen@sdaoden.eu> Sun, 14 April 2024 01:02 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 5E145C14F60F for <ietf-dkim@ietfa.amsl.com>; Sat, 13 Apr 2024 18:02:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.093
X-Spam-Level:
X-Spam-Status: No, score=-2.093 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_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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="DKCMAZiW"; dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=sdaoden.eu header.b="A6cBMU7X"
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 I1qBPmxD9kYR for <ietf-dkim@ietfa.amsl.com>; Sat, 13 Apr 2024 18:02:35 -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)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2CDEC14F5EA for <ietf-dkim@ietf.org>; Sat, 13 Apr 2024 18:02:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sdaoden.eu; s=citron; t=1713056551; x=1713723217; h=date:author:from:to: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=kzuZxXLUIpCNm1V/XUjcmqbWwUj7cG9SyhQrPOl0U+I=; b=DKCMAZiW72JRTl+xPXDG3wkB61WsDagyxg7FATfQGihklO9IEUk23XzviAjuF8KF3WfH/ddO p+aAjKHvNIyQqS1Ta5FyDYMLPJklRkVmbAVfGDz9BITCih93k18DHe7aKZ+8j+Y3C2OEBfJcop 8ovhaZAqNqOnMiR8Yrtn3WMLknRUiuS5nNWMZ85d2iKE36eAf3IVKZeVjgqsij5x5oS2sb8jcd odyyoBalq3wIkVRO06Sdmp+zf1bQofl44GD1IJoAZG4c6dd0IrLa6cxKrXblbBk62Bs2ByChlu 2xEMi68PwlHjCwI6t5A8pauCQCus09cJAC3RGaD5zxa6wOWA==
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=sdaoden.eu; s=orange; t=1713056551; x=1713723217; h=date:author:from:to: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=kzuZxXLUIpCNm1V/XUjcmqbWwUj7cG9SyhQrPOl0U+I=; b=A6cBMU7X5QGsEgdrMoFLq7/0RKE0Jz5BgNWAl04ZRHjluszxCgm27DRN5Lj2nc5mhXQPo0fh 79IHqPeyuofHDA==
Date: Sun, 14 Apr 2024 03:02:29 +0200
Author: Steffen Nurpmeso <steffen@sdaoden.eu>
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: ietf-dkim@ietf.org
Message-ID: <20240414010229.8kkHxNbU@steffen%sdaoden.eu>
In-Reply-To: <20240414005126.pzjJO4pr@steffen%sdaoden.eu>
References: <20240414005126.pzjJO4pr@steffen%sdaoden.eu>
Mail-Followup-To: 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/dHt0RA6VAdjDgglfFF-rgHmKJYM>
Subject: Re: [Ietf-dkim] RFC 8463: DNS textual form underspecified
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: Sun, 14 Apr 2024 01:02:41 -0000

Steffen Nurpmeso wrote in
 <20240414005126.pzjJO4pr@steffen%sdaoden.eu>:
 |Thanks to Hanno Böck (known from ossec and more) i was pointed to
 |my falsely published ED25519 DKIM key.
 |Until now that simply was the complete ED25519 public key, just
 |like for RSA, instead of extracting the actual "bitstring data"
 |from the standardized ASN.1 container, which starts at offset 16
 |(or -offset=12 if you use "openssl asn1parse -noout -out -" aka
 |the binary blob).
 |
 |I realize that RFC 8463 says repeatedly that the base64-encoded
 |representation of an ED25519 key is 44 bytes, and that the
 |examples go for this.  Still there is no wording that the entire
 |ASN.1 structure shall be thrown away.

That cannot be the reason Google, Microsoft and more do not
support that, right.  It is a bit bizarre that these huge RSA keys
are used all over the place, whereas the even stripped-naked ones
are not.

A nice Sunday i wish to everyone, if at all possible.
Ciao 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)