RE: SSL3_GET_RECORD:bad mac decode on SSLv23

PM To: [EMAIL PROTECTED] Cc: Amnon Cohen Subject: Re: SSL3_GET_RECORD:bad mac decode on SSLv23 Hi! I *think* the problem you are describing is actually on the server side. IIRC this is because your s_client by default will attempt to use TLS 1.0 (SSL 3.1), which the server incorrectly parses

SSL3_GET_RECORD:bad mac decode on SSLv23

, is there an argument to SSL_set_options() which will work around this bug? Many Thanks! Amnon Cohen __ OpenSSL Project http://www.openssl.org Development Mailing List [EMAIL PROTECTED

RE: SSL_connect and non-blocking reads (fwd)

Douglas Lee wrote: Hi Darkspell, I have 2 questions: 1) I have a multithreaded client which connects to the server using multiple sockets. How do I make the client verify the server certificate only once, say on the initial SSL_connect, and not for subsequent connects?

SSL_copy_session_id question

Hi folks, I am writing a yet another web browser. It uses multiple connection to download URLs simultaneously. (Not very original) How do I avoid each connection having to go through the full blown negotiation with the web server? Will SSL_copy_session_id do the job? What are the limitations

RE: SSL_connect() fails on non-blocking sockets.

Hi! Where did you get the man page for SSL_get_error() from? How can I find man pages for other SLL functions? Thanks Amnon Cohen -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 26, 2000 12:35 AM To: [EMAIL PROTECTED] Cc