On Út, 2016-10-11 at 16:46 +0000, Petr Pisar wrote:
> On 2016-10-11, Remi Collet <[email protected]> wrote:
> >
> > It doesn't seem possible to use a compat library (else we will very
> > probably going to encounter issues is both library versions are
> > used in
> > the same process, because of the numerous libraries linked to PHP
> > or its
> > extensions)
> >
> That's true. I was just porting a Perl package to OpenSSL 1.1.0 and
> while the ported code build and passed all tests when built against
> old
> OpenSSL, it crashed when linked to the new OpenSSL. The reason there
> was
> another Perl package loaded into the process that was linked to the
> old
> OpenSSL.
>
> Therefore I conclude it will be necessary to rebuild all packages
> requiring the old soname against new OpenSSL in the order of
> dependencies.
In my testing of application that pulled both old (indirectly) and new
OpenSSL (directly), it did not crash and I did not see anything wrong
with it. So it seems not all cases are broken however apparently the
above is reason for moving dependencies to 1.1.0 as quickly as
possible.
--
Tomas Mraz
No matter how far down the wrong road you've gone, turn back.
Turkish proverb
(You'll never know whether the road is wrong though.)
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]