On Mon, Jan 25, 2010, Frederick Shotton wrote:
> Hi Steve,
>
> I tried the new fix and it did not work for me. The Apache only fix did
> make renegotiation work however. The new fix hangs with the following
> output on s_client:
>
> New, TLSv1/SSLv3, Cipher is DHE-RSA-AES256-SHA
> Server public
Dr. Stephen Henson wrote:
> On Sat, Jan 23, 2010, Dr. Stephen Henson wrote:
>
>
>> On Fri, Jan 22, 2010, Michael Stone wrote:
>>
>>
>>> This certainly looks like a 12-byte verify_data field encoded as a
>>> variable-length vector (i.e. prefixed with a 1-byte length).
>>>
>>> 6.
On Sun, 24 Jan 2010 15:12:40 +0100, "Dr. Stephen Henson"
wrote:
> I've traced the cause this was *fun*. The full story is in:
>
> http://cvs.openssl.org/chngview?cn=19145
>
> This is a case of a bug in OpenSSL (PR#1949) being fixed but a related bug in
> Apache still existing in older versions.
egotiation handshake failed: Not accepted by client with
OpenSSL 0.98m-beta1
On Sat, Jan 23, 2010, Dr. Stephen Henson wrote:
>
> Just a quick note. I can reproduce this now and I'm investigating it further.
>
I've traced the cause this was *fun*. The full story is in:
ht
On Sat, Jan 23, 2010, Dr. Stephen Henson wrote:
> On Fri, Jan 22, 2010, Michael Stone wrote:
>
> >
> > This certainly looks like a 12-byte verify_data field encoded as a
> > variable-length vector (i.e. prefixed with a 1-byte length).
> >
> > 6. We receive a fatal unexpected_message
On Fri, Jan 22, 2010, Michael Stone wrote:
>
> This certainly looks like a 12-byte verify_data field encoded as a
> variable-length vector (i.e. prefixed with a 1-byte length).
>
> 6. We receive a fatal unexpected_message alert:
>
><<< TLS 1.0 Alert [length 0002], fatal une
On Fri, Jan 22, 2010, Michael Stone wrote:
> Dear openssl-users@ and, in particular, Dr. Henson,
>
> First, apologies that I didn't realize I was writing to you in my
> previous response to Fred. I'll check my To: lines more carefully in the
> future.
>
> Second, thanks for your earlier assista
Dear openssl-users@ and, in particular, Dr. Henson,
First, apologies that I didn't realize I was writing to you in my
previous response to Fred. I'll check my To: lines more carefully in the
future.
Second, thanks for your earlier assistance in diagnosing this
issue. Your suggestions have led me
On Wed, 20 Jan 2010 20:33:34 -0500, "Shotton, Fred" wrote:
> I'm running apache 2.2.14 with mod_ssl using OpenSSL 0.98m-beta1. When
> renegotiating a client session, I get an error from apache:
> "Re-negotiation handshake failed: Not accepted by client" and a fatal
> "unexpected_message" alert in
Dr. Stephen Henson wrote:
>
> On Wed, Jan 20, 2010, Shotton, Fred wrote:
>
> > I'm running apache 2.2.14 with mod_ssl using OpenSSL 0.98m-beta1.
> When renegotiating a client session, I get an error from apache:
> "Re-negotiation handshake failed: Not accepted by client" and a fatal
> "unexpected_m
On Wed, Jan 20, 2010, Shotton, Fred wrote:
> I'm running apache 2.2.14 with mod_ssl using OpenSSL 0.98m-beta1. When
> renegotiating a client session, I get an error from apache: "Re-negotiation
> handshake failed: Not accepted by client" and a fatal "unexpected_message"
> alert in OpenSSL s_cli
On Wed, Jan 20, 2010, Shotton, Fred wrote:
> I'm running apache 2.2.14 with mod_ssl using OpenSSL 0.98m-beta1. When
> renegotiating a client session, I get an error from apache: "Re-negotiation
> handshake failed: Not accepted by client" and a fatal "unexpected_message"
> alert in OpenSSL s_client
I'm running apache 2.2.14 with mod_ssl using OpenSSL 0.98m-beta1. When
renegotiating a client session, I get an error from apache: "Re-negotiation
handshake failed: Not accepted by client" and a fatal "unexpected_message"
alert in OpenSSL s_client. Below you will find log output for the renegoti
13 matches
Mail list logo
