Re: SSL3_GET_RECORD:bad mac decode on SSLv23

2001-10-11 Thread Oscar Jacobsson
Hi Amnon! IIRC, enabling TLSv1 in IE5 would result in not being able to connect to such a buggy server, which I assume would be for the same reason as with s_client. IE6 however seems to be able to connect, which I think (although this is only me guessing here) is due to it detecting the "bad ma

Re: SSL3_GET_RECORD:bad mac decode on SSLv23

2001-10-11 Thread Richard Levitte - VMS Whacker
c> amnonc> Thanks amnonc> Amnon amnonc> amnonc> -Original Message- amnonc> From: Oscar Jacobsson [mailto:[EMAIL PROTECTED]] amnonc> Sent: Wednesday, October 10, 2001 7:42 PM amnonc> To: [EMAIL PROTECTED] amnonc> Cc: Amnon Cohen amnonc> Subject: Re: SSL3_GE

RE: SSL3_GET_RECORD:bad mac decode on SSLv23

2001-10-11 Thread Amnon Cohen
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 as

Re: SSL3_GET_RECORD:bad mac decode on SSLv23

2001-10-10 Thread Oscar Jacobsson
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 as SSL 3.0 (ignoring the minor version number). TLS 1, which s_client assumes both parties have a