<div dir="ltr"><div>Hmm, doesn't make any difference on mine.</div><div>Googling I did fine some references that suggest that Qt networking loads libssl and libcrypto using dlopen, which would not show up as a dependency through ldd....</div><div><a href="https://code.qt.io/cgit/qt/qtbase.git/tree/src/network/ssl/qsslsocket_openssl_symbols.cpp">https://code.qt.io/cgit/qt/qtbase.git/tree/src/network/ssl/qsslsocket_openssl_symbols.cpp</a></div><div>So whilst ldd is listing that it is linked against 1.0 it may actually be picking up 1.1 from your library path.<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Sep 9, 2019 at 10:25 AM Dirk Hohndel <<a href="mailto:dirk@hohndel.org">dirk@hohndel.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Mon, Sep 09, 2019 at 10:03:44AM +0100, Dirk Hohndel wrote:<br>
> On Mon, Sep 09, 2019 at 09:50:07AM +0100, Paul Buxton wrote:<br>
> > Reviewing my log I also see an message Incompatible version of SSL<br>
> > <br>
> > Doing some googling this looks relevant.<br>
> > <a href="https://github.com/probonopd/linuxdeployqt/issues/209" rel="noreferrer" target="_blank">https://github.com/probonopd/linuxdeployqt/issues/209</a><br>
> > <br>
> > Basically it looks like Qt>5.10 expect to use openssl 1.1.<br>
> > The package we are supplying includes openssl 1.0<br>
> > I am guessing that on distros with newer versions of Openssl the Appimage<br>
> > is picking up the right version to use.<br>
> <br>
> Our emails crossed (i.e., I didn't see yours before sending mine). Yes,<br>
> that is a reasonable conclusion. Now I need to figure out if I even can<br>
> include an openssl 1.1 library with the Trusty based build...<br>
<br>
No, that isn't the problem:<br>
<br>
Let's force the AppImage to use the bundled openssl library... checking<br>
that this works:<br>
<br>
$ LD_LIBRARY_PATH=/tmp/.mount_SubsurMl62lz/usr/lib:$LD_LIBRARY_PATH ldd /tmp/.mount_SubsurMl62lz/AppRun  | grep ssl<br>
        libssl.so.1.0.0 => /tmp/.mount_SubsurMl62lz/usr/lib/libssl.so.1.0.0 (0x00007f55aeb85000)<br>
<br>
OK, so this picks up the included one<br>
<br>
$ LD_LIBRARY_PATH=/tmp/.mount_SubsurMl62lz/usr/lib:$LD_LIBRARY_PATH /tmp/.mount_SubsurMl62lz/AppRun  -v<br>
Subsurface v4.9.3,<br>
built with libdivecomputer v0.7.0-devel-Subsurface-NG (ce6d9896a79afaa82641132e338f8744714c8593)<br>
built with Qt Version 5.12.4, runtime from Qt Version 5.12.4<br>
built with libgit2 0.26.0<br>
[...]<br>
no SSL warnings<br>
[...]<br>
<br>
cloud URL set as "<a href="https://cloud.subsurface-divelog.org//git/dirk@hohndel.org%5Bdirk@hohndel.org%5D" rel="noreferrer" target="_blank">https://cloud.subsurface-divelog.org//git/dirk@hohndel.org[dirk@hohndel.org]</a>"<br>
Opening cloud storage from: "<a href="https://cloud.subsurface-divelog.org//git/dirk@hohndel.org%5Bdirk@hohndel.org%5D" rel="noreferrer" target="_blank">https://cloud.subsurface-divelog.org//git/dirk@hohndel.org[dirk@hohndel.org]</a>"<br>
git storage: Synchronising data file<br>
git storage: update local repo<br>
sync with remote <a href="https://cloud.subsurface-divelog.org//git/dirk@hohndel.org%5Bdirk@hohndel.org%5D" rel="noreferrer" target="_blank">https://cloud.subsurface-divelog.org//git/dirk@hohndel.org[dirk@hohndel.org]</a><br>
git storage: Sync with cloud storage<br>
Cloud storage: checking connection to cloud server<br>
Checking cloud connection...<br>
git storage: Waiting for cloud connection (1 second(s) passed)<br>
git storage: fetch remote<br>
git storage: Successful cloud connection, fetch remote<br>
git storage: check remote status<br>
git storage: try to update<br>
git storage: Done syncing with cloud storage<br>
git storage: Load dives from local cache<br>
git storage: Successfully opened dive data<br>
<br>
So there is something weird about that specific SSL library on your<br>
system, or more specifically there's something that our AppImage doesn't<br>
like.<br>
<br>
I don't think there's a way to force the AppImage to use its bundled SSL<br>
lib without mounting it - but this might be a workaround for now...<br>
<br>
/D<br>
</blockquote></div>