Hi,
this patch fixes a race condition (memory leak if not
worse) when multi-threading on a DSA* instance.
DSA_sign_setup() and DSA_do_verify() both have this
lazy eval code for the method_mont_p member. I added a
CRYPTO_w_lock(CRYPTO_LOCK_DSA) around it.
marius
PATCH-LOCK_DSA-openssl-0.9.7e.patch
Hello
As part of a project I am compiling OpenSSL on multiple different Unix
flavours and have had many different problems when trying to get OpenSSL
to compile.
So, I was wondering if anyone has done any work on minimum compiler
requirements on a per flavour basis:
IE:
Solaris 2.6, 2.7, 8, 9:
On Tue, Feb 01, 2005, Rafeeq Ahmed wrote:
> Thanks for ur respose
>
> But I still not satisfied
>
> I want the key as per RFC 2104 , http://www.faqs.org/rfcs/rfc2104.html
>
> which suggest the key to be between 20 to 64 bytes.
>
> Dave , is there any OpenSSL command which i can use to g
Thanks for ur respose
But I still not satisfied
I want the key as per RFC 2104 , http://www.faqs.org/rfcs/rfc2104.html
which suggest the key to be between 20 to 64 bytes.
Dave , is there any OpenSSL command which i can use to generate the
key directly or indirectly into char form
with
Any random data that is shared with the recipient will do as a key for HMAC
Dave
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Au
Hi
I am implementing HMAC algorithm
in which i need a private key in a unsigned char* format
the size of key required is between 20-64 bytes
can any one help me in this regard
with thanks
Rafeeq
__
OpenSSL Project