Problem connecting to OCSP server

2009-07-07 Thread Ashish Agrawal
Hi, I am using the openssl code for OCSP given in apps/ocsp.c. When i use this code to connect to an OCSP server which is present in my host system it connects, but when i try to connect to an network server it fails ? I want to know whether this program provides network based ocsp server

RE: Determining if client requests ssl handshake

2009-07-07 Thread David Schwartz
Howard Chu wrote: David Schwartz wrote: I've managed to do this without problems for SMTP, POP, HTTP, and a few custom text-based protocols. Note that the protocol must be such that the client sends data first. If the server must send data first, then there is no way for the

[openssl.org #1743]

2009-07-07 Thread John Wilkinson via RT
Any ETA on when this will make it into the upstream? __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager

[openssl.org #1743] crasher due to lack of threadsafety on names_lh

2009-07-07 Thread Stephen Henson via RT
[joh...@univaud.com - Tue Jul 07 22:39:32 2009]: Any ETA on when this will make it into the upstream? You aren't really supposed to call SSL_library_init(), OpenSSL_add_all_algorithms() et al from multiple threads simultaneously. It should be called before starting threads. If multiple

RE: [openssl.org #1743] crasher due to lack of threadsafety on names_lh

2009-07-07 Thread John Wilkinson via RT
That's a useful tip, perhaps, but if the underlying calls are embedded in a third-party libraries, such as handled by cURL etc, the end user has no choice as to when they're being initialized. Of course since multiple third-party libraries could be involved (which have no knowledge of each

[openssl.org #1743] crasher due to lack of threadsafety on names_lh

2009-07-07 Thread Stephen Henson via RT
[joh...@univaud.com - Tue Jul 07 23:01:13 2009]: That's a useful tip, perhaps, but if the underlying calls are embedded in a third-party libraries, such as handled by cURL etc, the end user has no choice as to when they're being initialized. Of course since multiple third-party libraries

RE: [openssl.org #1743] crasher due to lack of threadsafety on names_lh

2009-07-07 Thread John Wilkinson via RT
Thanks for the feedback on my patch - it includes locking in OBJ_NAME_cleanup and OBJ_NAME_remove, which seems to cover deinitialization. Where am I missing other cleanup that is not being properly mutexed? Certainly libraries could do bad things (like incorrectly using CRYPTO_NUM_LOCKS