Re: [Ietf-dkim] RFC 8463: DNS textual form underspecified
Scott Kitterman <ietf-dkim@kitterman.com> Sun, 14 April 2024 04:48 UTC
Return-Path: <ietf-dkim@kitterman.com>
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 0F5FFC14F617 for <ietf-dkim@ietfa.amsl.com>; Sat, 13 Apr 2024 21:48:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, 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=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=kitterman.com header.b="p9uea7+d"; dkim=pass (2048-bit key) header.d=kitterman.com header.b="F3mfBstX"
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 eSCAA9EDXxl8 for <ietf-dkim@ietfa.amsl.com>; Sat, 13 Apr 2024 21:47:57 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) (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 8C485C14F5EA for <ietf-dkim@ietf.org>; Sat, 13 Apr 2024 21:47:57 -0700 (PDT)
Received: from interserver.kitterman.com (interserver.kitterman.com [IPv6:2604:a00:6:1039:225:90ff:feaa:b169]) by interserver.kitterman.com (Postfix) with ESMTPS id EC126F801ED; Sun, 14 Apr 2024 00:47:44 -0400 (EDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903e; t=1713070050; h=date : from : to : subject : in-reply-to : references : message-id : mime-version : content-type : content-transfer-encoding : from; bh=y4HIw+mVsisN9HBAC14cv4L+dAHMm+oDSS/c6hIHj8E=; b=p9uea7+dTb5h1DmEx3g8uNIifhZCgOSqObUSpSTv7sENOA9sRMn0faWUr/b3IsQkqgBra rRNi9hlzYLYeq1RAg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kitterman.com; i=@kitterman.com; q=dns/txt; s=201903r; t=1713070050; h=date : from : to : subject : in-reply-to : references : message-id : mime-version : content-type : content-transfer-encoding : from; bh=y4HIw+mVsisN9HBAC14cv4L+dAHMm+oDSS/c6hIHj8E=; b=F3mfBstXgtu+z5/ZZVFU8B6e/b4cuKzTi1/dQtPhDQ3tDdvEufyFtABp8tEtzbLkVT9SU wpiILK30eNSJyXT6j4WjzyLtUzUKHscvND1aMfg3P6YcZAKltDc5knRwC7/DBASVCcHjoBs f7GTw9Nd8vH4eTpHZPk/bRlyothah/Tqff6HrjPiS+iUeP7NVx9TQnUjRX+75si6gpPa87S P/Xq0d4AbJIJwXu2/6PdaDzDPGZfY4Xd90KN/l8LBlD0/6LTc1tbOfWL9iKwrzwaT4rjlSf JvlNC6mzfBGSg1UvfRT5MYdkczoHFXAxPBLIIOjTPTJlwei1tcqW/vCqpCyQ==
Received: from [127.0.0.1] (static-72-81-252-22.bltmmd.fios.verizon.net [72.81.252.22]) by interserver.kitterman.com (Postfix) with ESMTPSA id DF041F80173; Sun, 14 Apr 2024 00:47:29 -0400 (EDT)
Date: Sun, 14 Apr 2024 04:47:25 +0000
From: Scott Kitterman <ietf-dkim@kitterman.com>
To: ietf-dkim@ietf.org
In-Reply-To: <20240414015307.JiO8yjFG@steffen%sdaoden.eu>
References: <20240414005126.pzjJO4pr@steffen%sdaoden.eu> <5368AC9A-51D5-4AEC-AB19-613DBEAD7C5B@kitterman.com> <20240414015307.JiO8yjFG@steffen%sdaoden.eu>
Message-ID: <2C92EB24-3332-436C-A0BB-D4BAC33220F2@kitterman.com>
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/9sqtTlaZw5SlK2yKERH_4MtvWSo>
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 04:48:02 -0000
On April 14, 2024 1:53:07 AM UTC, Steffen Nurpmeso <steffen@sdaoden.eu> wrote: >Scott Kitterman wrote in > <5368AC9A-51D5-4AEC-AB19-613DBEAD7C5B@kitterman.com>: > |On April 14, 2024 12:51:26 AM UTC, Steffen Nurpmeso <steffen@sdaoden.eu> \ > |wrote: > |>Hello. > |> > |>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. > | > |At the time we wrote what became RFC 8463, ASN.1 for ED25519 was not \ > |specified yet. Openssl didn't support ED25119 either. I'm not sure \ > |what you think we should have put in that we didn't. > | > |It seems to me that you are saying that the RFC is correct and clear, \ > |but that you were certain you knew better than the RFC. That's not \ > |a thing an RFC can fix. > >There *is* RFC 8410 to which 8463 refers, around the same time. >It defines exactly this, no? It says there are no further >parameters, but it does not say "hey so you can go and just leave >that niche container off". >Sure it is 44 bytes, but the entire thing is 64. >It is de-facto only the single example in A.2 which reveals the >total ignorance of ASN.1, and it is about brisbane and football, >which i cannot glue together (letting aside it is written by an >american, and who knows what kind of "football" that is?, as >i seem to know they say "soccer" for what i would think, but it is >4am so i do not truly think anyhow. Saturday night all right for >fighting, ah.) (OpenSSL in mid 2017, at least a bit.) >Thus: smart, very smart. Is always too smart for some. >Just leave them behind. I don't see it? Where is the reference to 8410? Scott K
- [Ietf-dkim] RFC 8463: DNS textual form underspeci… Steffen Nurpmeso
- Re: [Ietf-dkim] RFC 8463: DNS textual form unders… Steffen Nurpmeso
- Re: [Ietf-dkim] RFC 8463: DNS textual form unders… John Levine
- Re: [Ietf-dkim] RFC 8463: DNS textual form unders… Steffen Nurpmeso
- Re: [Ietf-dkim] RFC 8463: DNS textual form unders… Scott Kitterman
- Re: [Ietf-dkim] RFC 8463: DNS textual form unders… Steffen Nurpmeso
- Re: [Ietf-dkim] RFC 8463: DNS textual form unders… Scott Kitterman
- Re: [Ietf-dkim] RFC 8463: DNS textual form unders… Steffen Nurpmeso
- Re: [Ietf-dkim] RFC 8463: DNS textual form unders… Scott Kitterman
- Re: [Ietf-dkim] RFC 8463: DNS textual form unders… Steffen Nurpmeso