[Interest] QSslCertificate issues on FreeBSD
equeim at gmail.com
Tue Mar 21 03:00:33 CET 2023
>What about toDer()? The same?
I found out that this happens only if I install openssl via pkg. If I don't
do that it uses openssl from the base system and with that tests work (I
didn't know it existed in base so I installed it from pkg).
BTW test binary is linked to openssl (for reasons), while Qt AFAIK loads it
using dlopen. Not sure if it is relevant.
However even with openssl from pkg it still uses the same library when
linking and loading (/usr/local/lib/libcrypto.so.11). At least that's what
link_map::l_name (from dlinfo) says if I dlopen it manually.
I'm not sure what the issue is but I think I just won't install it from pkg
and hope it doesn't get pulled by dependencies.
пн, 20 мар. 2023 г. в 21:15, Elvis Stansvik <elvstone at gmail.com>:
> Den mån 20 mars 2023 kl 01:45 skrev Alexey Rochev <equeim at gmail.com>:
> > Hi,
> > I'm currently trying to add FreeBSD to my app's CI configuration and for
> some reason my tests fail due to QSslCertificate::operator==() returning
> false. More specifically, I compare a QSslCertificate loaded from PEM file
> and one returned from server (as extracted from QSslError). They are
> supposed to be the same, but their comparison returns false. Even more
> mysteriously, despite operator==() returning false,
> QSslCertificate::toPem() and QSslCertificate::toText() return exactly the
> same strings for both of them. This happens both with Qt 5.15.7 and 6.4.2.
> What about toDer()? The same?
> > I don't know whether there is an issue with my FreeBSD install (I
> haven't used it before) or somewhere else and would appreciate any help
> with this.
> > _______________________________________________
> > Interest mailing list
> > Interest at qt-project.org
> > https://lists.qt-project.org/listinfo/interest
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Interest