From: Martin Carpenter [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Memory problems in EVP_VerifyInit()?
Date: Thu, 2 Dec 2004 06:27:16 +0100
Hi there,
I have a couple of applications built upon a small library function
that I
have written. One of these applications works fine, all the time. The
other
[...snip...]
I am using MD5. In my debug output, I consistently obtain:
2.sig_len: [128]
3.sig_len: [271733878]
128 is the expected, computed, value. Why does calling
EVP_VerifyInit()
magically change the value of this local, non-passed integer?!
Now here's a thing:
$ printf %x\n 271733878
$ 10324576
The %x in the printf statement signifies conversion to hexadecimal
instead of printing decimal...
The number output matches what I get when I input the 2717... into my
hex converter and let it convert.
Regards,
Gregory Hicks
Those of you that are still awake may be reminded of Word A of RFC
3121 (MD5
spec).
Perhaps I did something stupid or missed something obvious?
__
OpenSSL Project http://www.openssl.org
User Support Mailing List[EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
-
Gregory Hicks | Principal Systems Engineer
Cadence Design Systems | Direct: 408.576.3609
555 River Oaks Pkwy M/S 6B1 | Fax: 408.894.3479
San Jose, CA 95134 | Internet: [EMAIL PROTECTED]
I am perfectly capable of learning from my mistakes. I will surely
learn a great deal today.
A democracy is a sheep and two wolves deciding on what to have for
lunch. Freedom is a well armed sheep contesting the results of the
decision. - Benjamin Franklin
The best we can hope for concerning the people at large is that they
be properly armed. --Alexander Hamilton
__
OpenSSL Project http://www.openssl.org
User Support Mailing List[EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]