Actually I'm looking for the EVP interface and I found out that 'The EVP interface should almost always be used in preference to the low level interfaces. This is because the code then becomes transparent to the algorithm used and much more flexible'. It might be true but...
...I would like to know, how can I use the low level functions for the example that I posted?! What am I missing? Anyone can help me? Dr. Stephen Henson wrote: > > On Fri, Oct 09, 2009, Kirk81 wrote: > >> >> Hello, >> >> I found your example of ECDSA_do_sign/verify very uselful. >> >> Now I'm trying to modify the code and I would like to use an SHA-256's >> message digest in your sign function. Something like: >> >> unsigned char obuf[32]; >> >> SHA-256(data, len, obuf); >> >> // now, in obuf there's the message digest (calculated using the SHA-256 >> function). >> >> but I have an error in the ECDSA_do_sign function when I pass the message >> digest in this way: >> sig = ECDSA_do_sign(obuf, 32, pkey); >> >> what's wrong? >> >> Problably I'm missing the conversion between data types: I mean, >> something >> used to convert the output of the SHA to an integer. In this case: which >> function should I use and how? >> > > I'd suggest you try OpenSSL 1.0.0 and the EVP interface instead. > > Steve. > -- > Dr Stephen N. Henson. OpenSSL project core developer. > Commercial tech support now available see: http://www.openssl.org > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > Development Mailing List openssl-dev@openssl.org > Automated List Manager majord...@openssl.org > > -- View this message in context: http://www.nabble.com/Bug-in-ECDSA_do_sign--tp1071562p25861215.html Sent from the OpenSSL - Dev mailing list archive at Nabble.com. ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
