Looks good to me.
Thanks for fixing it.
Best regards
Michael
On Oct 15, 2009, at 8:50 PM, Stephen Henson via RT wrote:
[steve - Thu Oct 15 20:37:17 2009]:
Erk, this breaks Win32 builds. The type in_port_t is not defined,
that
may be true of other platforms too.
I've committed a fix
On 2009.10.15 at 22:02:54 +0200, Roumen Petrov via RT wrote:
May be is good to document that numbers in hash dir starts from zero.
May be.
But just now I think it is much more important to get ANY documentation
for these functions into CVS.
At least it is quite easy to find out what number
The attached patch against 1.0.0 fixes a potential doublefree and reuse
of freed handshake_buffer when SSL_clear() is called.
--
Tomas Mraz
No matter how far down the wrong road you've gone, turn back.
Turkish proverb
--- s3_lib.c.hbuf-clear
The attached patch against 1.0.0 fixes a potential use
of freed SSL_CTX when SSL_free() is called after SSL_CTX_free()
in application.
--
Tomas Mraz
No matter how far down the wrong road you've gone, turn back.
Turkish proverb
diff -up
EVP_DigestInit (3) has a typo, as seen online here:
http://www.openssl.org/docs/crypto/EVP_DigestInit.html
It reads:
EVP_MD_CTX_init() initializes digest contet ctx.
EVP_MD_CTX_create() allocates, initializes and returns a digest contet.
The spell-checker reveals the typo contet which should be
Hi all,
I am writing a multi threaded server application which uses OpenSSL libraries
for communication. The server might have several instances running from a
single process (listening on several different ports and threads). My question
should I initialize open SSL for each of those servers
