Re: [openpgp] Deprecating SHA1

Ángel <angel@16bits.net> Wed, 28 October 2020 00:14 UTC

Return-Path: <angel@16bits.net>
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 D7A5B3A0992 for <openpgp@ietfa.amsl.com>; Tue, 27 Oct 2020 17:14:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 WQzT8HjXJvDw for <openpgp@ietfa.amsl.com>; Tue, 27 Oct 2020 17:14:47 -0700 (PDT)
Received: from mailer.hiddenmail.net (mailer.hiddenmail.net [199.195.249.9]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DF0B3A03F3 for <openpgp@ietf.org>; Tue, 27 Oct 2020 17:14:47 -0700 (PDT)
Received: from mailer by mailer.hiddenmail.net with local (Exim 4.80) (envelope-from <angel@16bits.net>) id 1kXZ70-0007zv-1Y for openpgp@ietf.org; Wed, 28 Oct 2020 01:14:46 +0100
Message-ID: <d1d9fb94cf2225157b367eb439d50271982f2e28.camel@16bits.net>
From: =?ISO-8859-1?Q?=C1ngel?= <angel@16bits.net>
To: openpgp@ietf.org
Date: Wed, 28 Oct 2020 01:14:44 +0100
In-Reply-To: <20201025010343.GA1089002@fullerene.field.pennock-tech.net>
References: <87sga5xg03.wl-neal@walfield.org> <20201023192317.GA444398@fullerene.field.pennock-tech.net> <87lffvy6kf.wl-neal@walfield.org> <20201025010343.GA1089002@fullerene.field.pennock-tech.net>
Content-Type: text/plain; charset="ISO-8859-15"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.30.5-1.1
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/ihpeJXJCNvVbYrEooYOAWwqFAr8>
Subject: Re: [openpgp] Deprecating SHA1
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: Wed, 28 Oct 2020 00:14:49 -0000

On 2020-10-24 at 21:03 -0400, Phil Pennock wrote:
> I think really we need some nice pgpkey-sanitycheck command-line
> tool, from any project, which looks purely at public key information,
> so doesn't need to care about internals (private keys, keyboxes,
> etc).
> 
> Such a tool might then report on outdated algorithms used in
> important places, while avoiding getting into the political mess of
> which algorithm order preferences should be included in a key.
> 
> I held off on "asking others to write software for me" in the
> previous post, keeping it to "this exists now".  This time around,
> I'm throwing out a "Hey, pgpkey-sanitycheck would be a nice tool to
> have, folks" and running away.

I too have thought in the past we should have a "pgplint" tool.¹
I have several ideas on what to measure (this community probably has
lots more), it's something I could do but didn't have the motivation to
start coding it.


¹ I don't know if Broadcom might dislike such name, though. Maybe it
should be called openpgp-lint, then?