Received-SPF: pass (google.com: domain of linux-crypto+bounces-4453-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Precedence: bulk
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8
Date: Tue, 28 May 2024 16:26:22 +0300
Message-Id: <D1LB8PVCTP1S.JDCEWNODTGTQ@kernel.org>
Cc: <linux-crypto@vger.kernel.org>, "David S. Miller" <davem@davemloft.net>,
 <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] crypto: ecdsa: Fix the public key format description
From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Stefan Berger" <stefanb@linux.ibm.com>, "Herbert Xu"
 <herbert@gondor.apana.org.au>
References: <20240527202840.4818-1-jarkko@kernel.org>
 <D1KQDPOZRWCW.1763CCYF1B84X@kernel.org>
 <D1KRILI1KRQ8.2CNPU7PFES0VI@kernel.org>
 <D1KRXI87G4S0.1ROKTQENIZHT7@kernel.org>
 <D1KS7LCALKD4.1J13QGYGZ6LBW@kernel.org>
 <D1KSLKGUWGFO.21T4OBXQQ88D@kernel.org>
 <D1KSSWD7FA94.5705Z3J7LKZA@kernel.org>
 <b5ff9003-065f-437f-bf6b-7f1ae0a0364a@linux.ibm.com>
In-Reply-To: <b5ff9003-065f-437f-bf6b-7f1ae0a0364a@linux.ibm.com>

On Tue May 28, 2024 at 3:37 PM EEST, Stefan Berger wrote:
>      Signature Value:
>          30:45:02:21:00:d9:d7:64:ba:5d:03:07:ee:20:a0:12:16:46:
>          31:e6:8e:66:0c:17:0d:74:07:87:58:5a:13:fc:14:62:98:9a:
>          99:02:20:59:ff:29:9c:52:b9:0a:35:3c:4b:03:bb:47:0e:c8:
>          3e:2d:cb:3e:1c:d3:51:88:91:b1:40:e3:03:86:1b:2a:e8
>
> 30:45 =3D> sequence containing 69 bytes
>    02:21: =3D> first coordinate with 0x21 bytes
>      00:d9 =3D> 0x21 bytes of ASN.1 integer with leading 0 to make the=20
> following 0x20-byte integer a positive number (its most significant bit=
=20
> is set).
>    02:20: =3D> int with 0x20 bytes
>     ...

This actually helped me located the bug in my code: I had 32 bytes for
the first one, with no leading zero. I.e. total length was off-by-one.

So I'll just extend either or both based on msb?=20

BR, Jarkko