On 2013-06-28 1:43, Dave Thompson wrote:
From: owner-openssl-us...@openssl.org On Behalf Of Lukas Haase
Sent: Thursday, 27 June, 2013 04:46
snip previous
I think I found the problem but I am unsure how to deal with it :-(
There are two ways to create a signature: The original message can
Dear Dave,
Thank you for your response!
On 2013-06-27 6:21, Dave Thompson wrote:
From: owner-openssl-us...@openssl.org On Behalf Of Lukas Haase
Sent: Tuesday, 25 June, 2013 19:13
I have the public and the private key for ECDSA on secp128r1 in a file
stored in PKCS8 format (saved with
From: owner-openssl-us...@openssl.org On Behalf Of Lukas Haase
Sent: Thursday, 27 June, 2013 04:46
snip previous
I think I found the problem but I am unsure how to deal with it :-(
There are two ways to create a signature: The original message can be
part of the signature (put=true) or not
Hi,
I have the public and the private key for ECDSA on secp128r1 in a file
stored in PKCS8 format (saved with Crypto++; it is PKCS8 according to
the Docu).
I can create a signature without an error but unfortunately it is not
validated successfully with my Crypto++ app:
$ cat testakt.txt |
From: owner-openssl-us...@openssl.org On Behalf Of Lukas Haase
Sent: Tuesday, 25 June, 2013 19:13
I have the public and the private key for ECDSA on secp128r1 in a file
stored in PKCS8 format (saved with Crypto++; it is PKCS8 according to
the Docu).
I can create a signature without an