Re: [INTERNALS-WIN] Re: PHP OpenSSL v0.9.8 compatibility issue with OpenSSL v1.0

From: Date: Thu, 13 Dec 2012 06:43:24 +0000
Subject: Re: [INTERNALS-WIN] Re: PHP OpenSSL v0.9.8 compatibility issue with OpenSSL v1.0
References: 1 2 3 4 5 6  Groups: php.internals.win 
Request: Send a blank email to internals-win+get-949@lists.php.net to get a copy of this message
On Thu, Dec 13, 2012 at 2:26 AM, Jan Ehrhardt <phpdev@ehrhardt.nl> wrote: > Hi Pierre, > > Pierre Joye in php.internals.win (Wed, 12 Dec 2012 23:51:46 +0100): >>The can't and won't is all about technical reasons. Mixing openssl >>versions leads to crashes. That's not fixable. > > What I am doing at the moment is not mixing OpenSSL versions at all. > Everything on my development servers is v1.0.1c. I am using the 1.0.1c > Apache binaries from Apachelounge, I am using my own PHP builds with > 1.0.1c and also for various other utilities like WinSCP I rely on > 1.0.1c. That's fine :) > There is a exception in my builds at the moment: Curl on Windows builds > flawlessly with_winssl, but for compilation with openssl you had to > tweak urldata.h (a conflict between ssh and ssl). Curl 7.28.1 seems to > build again with openssl (WITH_SSL=static WITH_SSH2=static > ENABLE_WINSSL=no). I will try to rebuild my PHP versions without WINSSL > in php_curl.dll. latest builds fine, that's what we use. Also winssl has some BC issues vs openssl (ca cert path for example) cannot be set. >>Basically we may or certainly will move to 1.x for 5.5. But we can't >>change it at this stage for 5.3 or 5.4. > > OK, your choice. 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, Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org

« previous php.internals.win (#949) next »