> Original Message
>From: Bruce Cran
>To: openssl-users@openssl.org
>Cc: "James"
>Sent: Thu, Feb 7, 2013, 9:48 AM
>Subject: Re: Issue with 1.0.1d with Apache 2.2.23
>
>On 07/02/2013 14:36, James wrote:
>>
>> Just an update, using a SS
ine with our current cipher suite.
This is probably the same bug that has been discussed recently - see
"Major OpenSSL 1.0.1d regression from 1.0.1c" on openssl-dev and ticket
2975 "Regression in OpenSSL 1.0.1d x86_64: Corrrupted data stream". From
that ticket:
"A ser
> Original Message
>From: "James"
>To: openssl-users@openssl.org
>Cc: openssl-users@openssl.org
>Sent: Wed, Feb 6, 2013, 3:51 PM
>Subject: Re: Issue with 1.0.1d with Apache 2.2.23
>
>> Original Message
>>From: "James"
>
> Original Message
>From: "James"
>To: openssl-users@openssl.org
>Sent: Wed, Feb 6, 2013, 2:50 PM
>Subject: Issue with 1.0.1d with Apache 2.2.23
>
>I recently upgraded our application to OpenSSL 1.0.1d with FIPS compiled in
>but disabled, which has alw
I recently upgraded our application to OpenSSL 1.0.1d with FIPS compiled in but
disabled, which has always been the case in the past. Our application runs in a
browser using Apache 2.2.23 and mod_ssl which is compiled against OpenSSL.
Testing has revealed that HTTP requests work fine, however
Thanks for the new release, and all the ongoing work.
How does the release relate to the source under git as viewed through
http://git.openssl.org/gitweb/ ? I don't see any mention of 1.0.1d in there,
and the latest change in 1_0_1-stable was 13 days ago.
Is the web view of the repos
