20.11.2016 в 21:29:35 +0100 Jan Niehusmann написал: > On Mon, Nov 21, 2016 at 12:02:45AM +0400, Stepan Golosunov wrote: > > It would be a grave bug in such application if it does not have a > > working version, yes. Whether or not it would be a serious bug in > > lubcurl3 depends on how many and how important such applications are. > > (And how difficult they are to fix.) > > As there are applications which depend on libcurl and qt, and it seems > like qt can't be ported to openssl 1.1 in time for stretch, fixing such > applications would mean uploading a version of curl linked to openssl > 1.0. This could be a new package, or a statically linked version etc. - > IMHO all worse than just linking the curl package with openssl 1.0 until > (close to) all packages are ready for a transition to openssl 1.1.
So far I do not know why using libssl1.1 together with a libssl1.0.2-using Qt wouldn't work. So far I can imagine the following reasons: 1. Application relies on Qt initializing the library. That was the cause of breakage during libssl1.0.0 -> libssl1.0.2 transition, but is not applicable now as libssl1.1 does not require explicit initialization. 2. Application passes OpenSSL objects from libssl1.1 to Qt (or vice versa). Why one would do it? 3. dlsym(3) is used with RTLD_DEFAULT or RTLD_NEXT. Does not seem to be the case. 4. dlsym(3) finds wrong library. Manual page suggests that should not be the case. … Is any of the above applicable?
