Re: [INTERNALS-WIN] Re: PHP OpenSSL v0.9.8 compatibility issue with OpenSSL v1.0
| From: | Pierre Joye | Date: | Fri, 14 Dec 2012 09:18:51 +0000 |
| Subject: | Re: [INTERNALS-WIN] Re: PHP OpenSSL v0.9.8 compatibility issue with OpenSSL v1.0 | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.internals.win |
| Request: | Send a blank email to internals-win+get-952@lists.php.net to get a copy of this message | ||
hi,
On Thu, Dec 13, 2012 at 8:10 AM, Jan Ehrhardt <phpdev@ehrhardt.nl> wrote:
> Pierre Joye in php.internals.win (Thu, 13 Dec 2012 07:43:24 +0100):
>>Also winssl has some BC issues vs openssl (ca cert path for example)
>>cannot be set.
>
> But OpenSSL 0.9.x has a issue with connecting to a v1.0.1c server, using
> Curl. This typically looks like a problem in between parties. PHP relies
> on Curl, Daniel Stenberg (Curl, badger on sourceforge) thinks it is a
> OpenSSL issue, Paul Donohue thinks Apache has to solve it
>
> <http://sourceforge.net/p/curl/bugs/1037/?limit=10&page=1#aa7f>,
> but
> nobody ever steps in.
Welcome to the OpenSSL world. I seriously consider to move to winssl
only in 6.x. If we manage to support the same set of features.
>>No, not my choice, that's about BC and compatibility with 3rd parties.
>>If we change that now they will have to provide extra binaries for the
>>same branches, that's not acceptable and against the ABI/API policy,
>
> Just curious: what 3rd parties are you talking about?
Any 3rd parties providing extensions for PHP and reliying on OpenSSL.
That's quite a lot.
Cheers,
--
Pierre
@pierrejoye