Bug#827061: transition: openssl
On 2016-10-26 21:31:26 [+0200], Kurt Roeckx wrote:
> > Is this situation
> > supported or should we expect things to break? This can easily happen if an app
> > links against a library libA which uses openssl 1.0, and against libB which uses
> > openssl 1.1.
> When linking you actually get a warning.
> As far as I know, it should only break when they use dlopen().
> They most likely won't be using dlvsym() in that case and then it
> can pick any version. It could of course also break if they do
> very weird things.
One of the weird things would be probably if libA allocate a SSL pointer
and passes it to libB.