Re: Investigating a leak

On Jul 18, 2005, at 18:57, Simon Edwards wrote: I don't know if it helps you much, but since the FAQ is a bit cryptic it may help. I've used... ERR_remove_state() ...at the end of each thread. Doing this. Plus... CRYPTO_cleanup_all_ex_data() CONF_modules_free() ERR_free_strings() EVP_c

Re: Investigating a leak

On Jul 18, 2005, at 14:11, Amar Desai wrote: http://www.openssl.org/support/faq.html Search for the words *memory leak* Yes, thank you, indeed I have read that, and I am using ERR_remove_state() at the end of the thread. Looks to me like the other functions should be used before terminati

Investigating a leak

Hello, I'm investigating a leak in a server application, which I've managed to reduce to a test case which involves OpenSSL and threads. I've put the code up at http://www.zankasoftware.com/ssltest/server.c if anyone would be willing to take a look and see what I'm doing wrong. Every time

Re: Securing small UDP transmissions

rvers per tracker. Thanks for the reply, Axel Andersson __ OpenSSL Project http://www.openssl.org User Support Mailing List[EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]

/dev/random and chroot()

root directory? Thanks in advance, Axel Andersson -- [EMAIL PROTECTED] http://www.animanga.nu/morris/ __ OpenSSL Project http://www.openssl.org User Support Mailing List[