Message-ID: <4F22EACA.2080807@netmind.hu>
Date: Fri, 27 Jan 2012 19:19:54 +0100
From: =?ISO-8859-1?Q?Brautigam_R=F3bert?= <robert.brautigam@netmind.hu>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
	rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
References: <4F1DBD07.3050904@netmind.hu> <4F1EEB6D.8080004@netmind.hu>
In-Reply-To: <4F1EEB6D.8080004@netmind.hu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Bitcoin-development] ECC Signature Issue
Precedence: list

Hi,

I'll reply to myself here, just to mention that the issue is solved.

Dave Hook from Bouncycastle replied that in the particular signature=20
mentioned, one of the ASN1 encoded Integers is actually negative (which=20
is not a valid coordinate for a point on a curve I assume). Since ASN1=20
integers are always signed, one has to pad "big" values with a zero byte=20
to stay positive.

Workaround is easy for verification (convert to positive).

Robert.

On 01/24/2012 06:33 PM, Brautigam R=F3bert wrote:
> On 01/23/2012 06:50 PM, Mike Hearn wrote:
>>> I double checked that the official (C++) client is indeed successful
>>> here. Oddly enough the bitcoinj implementation also seems to fail to
>>> verify this transaction, which seems to point in the direction of
>>> BouncyCastle (which we both use).
...