Re: [openpgp] v5 in the crypto-refresh draft

Paul Wouters <paul@nohats.ca> Sat, 05 June 2021 18:16 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 454A53A2B39 for <openpgp@ietfa.amsl.com>; Sat, 5 Jun 2021 11:16:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 a_Pb6WpW2azE for <openpgp@ietfa.amsl.com>; Sat, 5 Jun 2021 11:16:17 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 610033A2B34 for <openpgp@ietf.org>; Sat, 5 Jun 2021 11:16:17 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 4Fy79p3q0pzFHR for <openpgp@ietf.org>; Sat, 5 Jun 2021 20:16:14 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1622916974; bh=uDlSkP7XCnZO1v1aq4U9SwywND+vxr5sy/+jKwEa/ug=; h=Date:From:To:Subject:In-Reply-To:References; b=Oumo13AuOUQIaCqoGv/UHrBr0GKCeAngPi29RdDNoQAe5nEcRcMNrgJRE6TeDNbr8 c8VPF5m/DiPWW1zinzzl432BjO2lqe7DZDd1TuLWzNCYfcXyZKt6MWSxsOH03i0+PJ BdC/SI99g9SEaX8N5jMtOb7456x5W/HKenP2vOnM=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id oDBvI-e8yVLh for <openpgp@ietf.org>; Sat, 5 Jun 2021 20:16:13 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [193.110.157.194]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS for <openpgp@ietf.org>; Sat, 5 Jun 2021 20:16:13 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 04D507D716; Sat, 5 Jun 2021 14:16:12 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 005447D715 for <openpgp@ietf.org>; Sat, 5 Jun 2021 14:16:11 -0400 (EDT)
Date: Sat, 5 Jun 2021 14:16:11 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: openpgp@ietf.org
In-Reply-To: <87sg1wqjrl.fsf@fifthhorseman.net>
Message-ID: <3c983dd-996d-98b-3593-abd046472cd3@nohats.ca>
References: <87lf7q6sh0.fsf@fifthhorseman.net> <CehzUzKNsBcldCQuRadnyAgV7hLQR1cve61qHfJYP-_cTKGeKTAMVo1GUdmbIL0AumFM9-XizsIiI8KAZvs44WILEG3FbHxM6aSTk7tSGzg=@protonmail.com> <SY4PR01MB62516FFB629BC19330E9129CEE3A9@SY4PR01MB6251.ausprd01.prod.outlook.com> <87sg1wqjrl.fsf@fifthhorseman.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/G1mS1QoojZoQqLlZ5Burqi0LAa4>
Subject: Re: [openpgp] v5 in the crypto-refresh draft
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Jun 2021 18:16:22 -0000

On Sat, 5 Jun 2021, Daniel Kahn Gillmor wrote:

> Furthermore, having to constantly
> defend the use of SHA-1 when it is known to be deprecated *in other
> contexts* is a tiresome exercise, and i think it'd be great if the
> OpenPGP community could move past it.

This is the main argument for me. Crypto libraries are trying to phase
out and disable SHA-1. Some crypto libraries have API's that allow
the caller to say "yes I know, you can trust my use of it" but not
all libraries have that. So it is useful to just move from SHA-1 to
SHA2 for this reason alone.

Paul