IETF Logo Mail Archive

Re: [xml2rfc-dev] cryptographic signatures over xml2rfc releases should not be made with SHA1

Daniel Kahn Gillmor <dkg@fifthhorseman.net> Wed, 17 March 2021 21:02 UTC

Return-Path: <dkg@fifthhorseman.net>
X-Original-To: xml2rfc-dev@ietfa.amsl.com
Delivered-To: xml2rfc-dev@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 016C13A14CC for <xml2rfc-dev@ietfa.amsl.com>; Wed, 17 Mar 2021 14:02:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=fifthhorseman.net header.b=Dt1n7eYF; dkim=pass (2048-bit key) header.d=fifthhorseman.net header.b=YPjAo3nD
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 qUyRdRBq5uTv for <xml2rfc-dev@ietfa.amsl.com>; Wed, 17 Mar 2021 14:02:24 -0700 (PDT)
Received: from che.mayfirst.org (che.mayfirst.org [IPv6:2001:470:1:116::7]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C2B83A14CB for <xml2rfc-dev@ietf.org>; Wed, 17 Mar 2021 14:02:24 -0700 (PDT)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019; t=1616014940; h=from : to : subject : in-reply-to : references : date : message-id : mime-version : content-type : from; bh=4XUfq3qDPZO0xqlUErizJTb7oSV6gS80EzrtJLqQ9Vc=; b=Dt1n7eYFuW+kUnmPj1xxQt3HwP++z/hdrxiZ/eRP4lQ02bpLbwk4GAuK9M8ul+9BH1DT4 l0BurlWmEYYTKMNBw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019rsa; t=1616014940; h=from : to : subject : in-reply-to : references : date : message-id : mime-version : content-type : from; bh=4XUfq3qDPZO0xqlUErizJTb7oSV6gS80EzrtJLqQ9Vc=; b=YPjAo3nDD6J+KrldWDXphkfKrufX++DWhyULe9y1f5VPknO1c363UACXGsGyZh1Qguc3z 29UyoD+M93y01O5MUGkRLh7JRsPSTRDmHnIOF7iuF0Kt0lFcBvTqLDJ8LkiLke98L12UPLx GFDSzRR4/fgikMuW+C1dtVRc1VqMo5KZgXtvwfYUybRxdxVLp6y4Ep5g4cHflVMm+j6kSqD 224BU1EZcuVhid3tUyG+Me+vt4gmhaUmAoqCM61erBbuGQmX6DwQfV8lpSz14LB/5aDmHb9 seyWoCZR5X/oHdzCN8W6TFBzNU4V7AvH0CqlTRRXVsB4SM67zH8dfFUMwVqA==
Received: from fifthhorseman.net (lair.fifthhorseman.net [108.58.6.98]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by che.mayfirst.org (Postfix) with ESMTPSA id 4360DF9A5; Wed, 17 Mar 2021 17:02:20 -0400 (EDT)
Received: by fifthhorseman.net (Postfix, from userid 1000) id AC58A20415; Wed, 17 Mar 2021 17:02:17 -0400 (EDT)
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Robert Sparks <rjsparks@nostrum.com>, xml2rfc-dev@ietf.org
In-Reply-To: <bc672b51-c624-5e38-de55-fe13c0439fee@nostrum.com>
References: <87y2flrr5y.fsf@fifthhorseman.net> <bc672b51-c624-5e38-de55-fe13c0439fee@nostrum.com>
Autocrypt: addr=dkg@fifthhorseman.net; prefer-encrypt=mutual; keydata= mDMEX+i03xYJKwYBBAHaRw8BAQdACA4xvL/xI5dHedcnkfViyq84doe8zFRid9jW7CC9XBiI0QQf FgoAgwWCX+i03wWJBZ+mAAMLCQcJEOCS6zpcoQ26RxQAAAAAAB4AIHNhbHRAbm90YXRpb25zLnNl cXVvaWEtcGdwLm9yZ/tr8E9NA10HvcAVlSxnox6z62KXCInWjZaiBIlgX6O5AxUKCAKbAQIeARYh BMKfigwB81402BaqXOCS6zpcoQ26AADZHQD/Zx9nc3N2kj13AUsKMr/7zekBtgfSIGB3hRCU74Su G44A/34Yp6IAkndewLxb1WdRSokycnaCVyrk0nb4imeAYyoPtBc8ZGtnQGZpZnRoaG9yc2VtYW4u bmV0PojRBBMWCgCDBYJf6LTfBYkFn6YAAwsJBwkQ4JLrOlyhDbpHFAAAAAAAHgAgc2FsdEBub3Rh dGlvbnMuc2VxdW9pYS1wZ3Aub3JnL0Gwxvypz2tu1IPG+yu1zPjkiZwpscsitwrVvzN3bbADFQoI ApsBAh4BFiEEwp+KDAHzXjTYFqpc4JLrOlyhDboAAPkXAP0Z29z7jW+YzLzPTQML4EQLMbkHOfU4 +s+ki81Czt0WqgD/SJ8RyrqDCtEP8+E4ZSR01ysKqh+MUAsTaJlzZjehiQ24MwRf6LTfFgkrBgEE AdpHDwEBB0DkKHOW2kmqfAK461+acQ49gc2Z6VoXMChRqobGP0ubb4kBiAQYFgoBOgWCX+i03wWJ BZ+mAAkQ4JLrOlyhDbpHFAAAAAAAHgAgc2FsdEBub3RhdGlvbnMuc2VxdW9pYS1wZ3Aub3Jnfvo+ nHoxDwaLaJD8XZuXiaqBNZtIGXIypF1udBBRoc0CmwICHgG+oAQZFgoAbwWCX+i03wkQPp1xc3He VlxHFAAAAAAAHgAgc2FsdEBub3RhdGlvbnMuc2VxdW9pYS1wZ3Aub3JnaheiqE7Pfi3Atb3GGTw+ jFcBGOaobgzEJrhEuFpXREEWIQQttUkcnfDcj0MoY88+nXFzcd5WXAAAvrsBAIJ5sBg8Udocv25N stN/zWOiYpnjjvOjVMLH4fV3pWE1AP9T6hzHz7hRnAA8d01vqoxOlQ3O6cb/kFYAjqx3oMXSBhYh BMKfigwB81402BaqXOCS6zpcoQ26AADX7gD/b83VObe14xrNP8xcltRrBZF5OE1rQSPkMNy+eWpk eCwA/1hxiS8ZxL5/elNjXiWuHXEvUGnRoVj745Vl48sZPVYMuDgEX+i03xIKKwYBBAGXVQEFAQEH QIGex1WZbH6xhUBve5mblScGYU+Y8QJOomXH+rr5tMsMAwEICYjJBBgWCgB7BYJf6LTfBYkFn6YA CRDgkus6XKENukcUAAAAAAAeACBzYWx0QG5vdGF0aW9ucy5zZXF1b2lhLXBncC5vcmcEAx9vTD3b J0SXkhvcRcCr6uIDJwic3KFKxkH1m4QW0QKbDAIeARYhBMKfigwB81402BaqXOCS6zpcoQ26AAAX mwD8CWmukxwskU82RZLMk5fm1wCgMB5z8dA50KLw3rgsCykBAKg1w/Y7XpBS3SlXEegIg1K1e6dR fRxL7Z37WZXoH8AH
Date: Wed, 17 Mar 2021 17:02:16 -0400
Message-ID: <87v99p5w9z.fsf@fifthhorseman.net>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xml2rfc-dev/9IpQg9OO9h-NvJcAegHPbHITDfA>
Subject: Re: [xml2rfc-dev] cryptographic signatures over xml2rfc releases should not be made with SHA1
X-BeenThere: xml2rfc-dev@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion about particulars of xml2rfc V3 design, development and code." <xml2rfc-dev.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xml2rfc-dev/>
List-Post: <mailto:xml2rfc-dev@ietf.org>
List-Help: <mailto:xml2rfc-dev-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xml2rfc-dev>, <mailto:xml2rfc-dev-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Mar 2021 21:02:26 -0000

Hi Robert--

On Wed 2021-03-17 14:26:54 -0500, Robert Sparks wrote:

> You'll have seen that 3.6.0 was just released, and this comment has not 
> yet been addressed.
>
> It's on the list to deal with. I wanted to make sure you knew this 
> wasn't being ignored.

Thanks for the heads-up, and for the stated intent to fix the issue.
Let me know if there's anything i can do to help the process of fixing
this, including by private mail if you like.

As one of the debian maintainers of GnuPG, and as a co-chair of the
OpenPGP WG, i can hopefully give reasonably useful advice in multiple
domains: practical tooling guidance, system integration advice,
theoretical explanations, and protocol level detail.  lemme know if you
need any of it.

         --dkg

v2.23.0 | Report a Bug | By Email