I wouldn’t say I’m stuck… just overwhelmed with unfamiliar code.  I’ll post to 
the list so everyone can benefit.

I found a good starting point…  here is some C++ and OpenSSL sourcecode that 
will assist with the conversion
https://github.com/bitcoin/bitcoin/blob/9b1200c23bbced3a78b58067c1f6414103653795/src/key.cpp#L56

I’m still learning ECC and the math behind it, not to mention I’m unfamiliar 
with the OpenSSL stack and learning BC; I have a way to go.

Also related: my question on Stack Overflow.
http://stackoverflow.com/q/19665491/328397

From: Peter Dettman [mailto:[email protected]]
Sent: Wednesday, October 30, 2013 3:52 AM
To: Bouncy Castle Developer List
Subject: Re: [dev-crypto-csharp] ECDSA Key recovery (SEC1 4.1.6) for curves 
over (mod p)-fields

I don't believe we have support for this, though it doesn't look that difficult 
to implement. We'd be happy to include it in the library.

I think the ECDomainParameters class has all the magic numbers you need, in 
combination with the r, s values and the message. Feel free to email me, or 
post to the list if you get stuck.

Regards,
Pete Dettman

On 30/10/2013 6:20 AM, Mankowski, Chris wrote:
I知 looking for a way to extract an ECDSA key from a signature as shown in the 
C++ code below

http://github.com/bitcoin/bitcoin/blob/9b1200c23bbced3a78b58067c1f6414103653795/src/key.cpp

Does Bouncy Castle now, or in the future offer this feature?

The problem I知 trying to solve is validating a Bitcoin transaction, and a 
message that comes from the Bitcoin-QT client.

If anyone can point me in the right direction, or assist in porting this 
function over to BouncyCastle I壇 be greatly appreciative.
________________________________
Notice: This e-mail message and any attachment to this e-mail message may 
contain information that is confidential, proprietary, privileged, legally 
privileged and/or exempt from disclosure under applicable law. If you are not 
the intended recipient, please accept this as notice that any disclosure, 
copying, distribution or use of the information contained in this transmission 
is strictly prohibited. NFP reserves the right, to the extent and under 
circumstances permitted by applicable law, to retain, monitor and intercept 
e-mail messages to and from its systems.

Any views or opinions expressed in this e-mail are those of the sender and do 
not necessarily express those of NFP. Although this transmission and any 
attachment are believed to be free of any virus or other defect that might 
affect any computer system into which it is received and opened, it is the 
responsibility of the recipient to ensure that it is virus free and no 
responsibility is accepted by NFP, its subsidiaries and affiliates, as 
applicable, for any loss or damage arising in any way from its use.

If you have received this e-mail in error, please immediately contact the 
sender by return e-mail or by telephone at 212-301-4000 and destroy the 
material in its entirety, whether electronic or hard copy format.

Reply via email to