> > Make sure QSslSocket::supportSsl() returns true. You have to ship the
> > OpenSSL
> > 1.1 libraries yourself, they are not part of Qt, not even of the pre-built
> > binaries.
>
Done - work like a charm. Simply needed to include
libeay32.dll
ssleay32.dll
into the main app's folder. Than
> Sorry, I might be missing some critical piece of information: is it a browser
> that is connecting to your websocket service? I thought it was a web view,
> whose CA list you could control.
The most simple way to describe it this:
A conventional html page (classical web browser) launches a we
On Sunday, 2 August 2020 16:09:32 PDT Hamish Moffatt wrote:
> On 3/8/20 9:05 am, Alexander Carôt wrote:
> >> I repeat: whatever you do, don't ship a private key.
> >
> > Allright - will consider alternative ideas.
>
> Consider generating your own root CA certificate and asking your users
> to ins
