Re: [CFRG] Proposed resolution for erratum 5930 on RFC 8032

Mike Hamburg <mike@shiftleft.org> Fri, 15 January 2021 18:43 UTC

Return-Path: <mike@shiftleft.org>
X-Original-To: cfrg@ietfa.amsl.com
Delivered-To: cfrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A4103A1086 for <cfrg@ietfa.amsl.com>; Fri, 15 Jan 2021 10:43:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.306
X-Spam-Level:
X-Spam-Status: No, score=-1.306 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, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=shiftleft.org
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 GQgbNYZ0wo_s for <cfrg@ietfa.amsl.com>; Fri, 15 Jan 2021 10:43:21 -0800 (PST)
Received: from astral.shiftleft.org (unknown [54.219.126.124]) (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 D790C3A1083 for <cfrg@irtf.org>; Fri, 15 Jan 2021 10:43:21 -0800 (PST)
Received: from [192.168.86.39] (unknown [209.240.35.59]) (Authenticated sender: mike) by astral.shiftleft.org (Postfix) with ESMTPSA id 7FD32BB80B; Fri, 15 Jan 2021 18:43:20 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=shiftleft.org; s=sldo; t=1610736201; bh=tPyi6vxOSK1s8+aubFSZs1ztqTNRLrEugEVX3KKW5CE=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=f1xfoUgZ0cexxEZmQr8L6IMidnSv7wgoaC7wC7LvzgBWStBaebh6XXfsCzAOqvzph 1KtmI6DEIEaxRKCuspZ7t2MHkyifxQ4EYzg72I4FvFNZpcMmnt0KuTHghKsZWoEfdf 0VI3uYv45RHhIclXD3Q9Iam3e/hbpPv5xM5TqFBU=
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
From: Mike Hamburg <mike@shiftleft.org>
In-Reply-To: <5B7E3193-C020-48AC-8C1F-E11D7924250F@josefsson.org>
Date: Fri, 15 Jan 2021 14:43:18 -0400
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, CFRG <cfrg@irtf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <1A0AAD7B-21FC-4611-8C0E-3C231A7F441B@shiftleft.org>
References: <42fdca41-bfdd-9d75-b144-0e2f3b5fa1d9@isode.com> <5B7E3193-C020-48AC-8C1F-E11D7924250F@josefsson.org>
To: Simon Josefsson <simon=40josefsson.org@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cfrg/EHXgAIgQJYnLipO12XI1RXvm6Bs>
Subject: Re: [CFRG] Proposed resolution for erratum 5930 on RFC 8032
X-BeenThere: cfrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Crypto Forum Research Group <cfrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/cfrg>, <mailto:cfrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cfrg/>
List-Post: <mailto:cfrg@irtf.org>
List-Help: <mailto:cfrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/cfrg>, <mailto:cfrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jan 2021 18:43:24 -0000

I also agree.  — Mike

> On Jan 15, 2021, at 1:42 PM, Simon Josefsson <simon=40josefsson.org@dmarc.ietf.org> wrote:
> 
> +1
> 
> /Simon
> 
>> 15 jan. 2021 kl. 18:39 skrev Alexey Melnikov <alexey.melnikov@isode.com>om>:
>> 
>> Dear CFRG (and editors),
>> 
>> Daniel Bleichenbacher submitted the following editorial erratum on RFC 8032 ("Edwards-Curve Digital Signature Algorithm (EdDSA)")
>> 
>> Section 6 says:
>> 
>> OLD:
>> 
>> def verify(public, msg, signature):
>>    if len(public) != 32:
>>        raise Exception("Bad public key length")
>>    if len(signature) != 64:
>>        Exception("Bad signature length")
>> 
>> It should say:
>> 
>> def verify(public, msg, signature):
>>    if len(public) != 32:
>>        raise Exception("Bad public key length")
>>    if len(signature) != 64:
>>        raise Exception("Bad signature length")
>> 
>> 
>> Note: Missing raise before Exception
>> 
>> -------------------
>> 
>> This is indeed looks like a Python syntax error. So I propose to resolve this erratum as suggested by Daniel.
>> 
>> Please provide your feedback by the end of January 29th.
>> 
>> 
>> Best Regards,
>> 
>> Alexey, as a co-chair
>> 
>> 
> 
> _______________________________________________
> CFRG mailing list
> CFRG@irtf.org
> https://www.irtf.org/mailman/listinfo/cfrg