[Pkg-openssl-devel] Processed: Re: Bug#623596: mumble: Problem with the import certificats

[Kurt Roeckx]

On Tue, Apr 26, 2011 at 01:08:31AM -0700, Thorvald Natvig wrote:
> On 24.04.2011 15:00, Kurt Roeckx wrote:
> 
> > 
> > dlopen will cause problems if you don't use dlvsym() to select the
> > right version.  It's very unlikely dlvsym() is used, and it
> > probably just uses dlsym() instead.
> 
> Indeed. But that should only cause a problem for Qt; the problem here is
> that using the PKCS12 functions fails from Mumble, which explicitly
> links libssl and libcrypto. So it's the 1.0.0 version, which is linked
> "normally", that fails.

Once you loaded a function without version, you're basicly screwed.

> > Why doesn't it open the 0.9.8 soname and not the 1.0.0 one?  Is
> > that hardcoded or something?
> 
> I did some digging in Qt source and found this:
> libssl->setFileNameAndVersion(QLatin1String("ssl"),QLatin1String(SHLIB_VERSION_NUMBER));
> 
> SHLIB_VERSION_NUMBER is defined by the openssl headers. In other words,
> it tries to runtime load the same version is was compiled with. Which
> sort of makes sense. However, the code seems to indicate it should fall
> back gracefully. It does, in a sense; it happily loads the 1.0.0 version
> of the library, but it doesn't work with it :(
> 
> I'm guessing a recompile of Qt will fix this. I'll give that a shot and
> see if it improves things.

There wasn't a binNMU for qt4-x11 because libqt4-network does not
depend on libssl, nor is there a build-dependency on it.  So why
does it use it?


Kurt