[Interest] Qt for WinRT and openssl

Maurice Kalinowski Maurice.Kalinowski at qt.io
Fri Mar 16 07:06:58 CET 2018


I’ll let Oliver provide the detailed answer, but the history as such is:

  *   WinRT uses a new networking API. When released Winsock was not only deprecated but disallowed to be used
  *   We implemented network features using that new API.
  *   In the meantime there were sufficient complaints/feature requests, that Microsoft created a new OpenSSL fork (https://bugreports.qt.io/browse/QTBUG-51871 )
  *   A bit later, Winsock2 has been allowed to be used in WinRT (which is called UWP now) again.
  *   The aim is to rather use this in Qt as well, as it shares then the desktop/classic implementation, which gives bigger coverage.

In the meantime we are using the new, but not widely adopted API. SSL is handled via the platform capabilities similar to what we do on mac. If you encounter a specific issue, please create a bugreport and we will follow up there.


From: Interest [mailto:interest-bounces+maurice.kalinowski=qt.io at qt-project.org] On Behalf Of Rogerio Nicolau
Sent: Thursday, March 15, 2018 4:21 PM
To: interest at qt-project.org
Subject: [Interest] Qt for WinRT and openssl


The WinRT platform version of ssl seems to be very limited and doesn't work when accessing web services with certain ssl certificates.

On Android I am using the openssl library successfully so I wanted to use this on WinRT as well. I have built the openssl libraries and included them in the build but it still seems to use the platform ssl version. (I have tried on Qt 5.9 and 5.10)
I used the Microsoft openssl (https://github.com/Microsoft/openssl) version 1.0.2.

Is using openssl supported in Qt for WinRT and if so do I need to do anything else to get it to use those libs?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20180316/411d06a4/attachment.html>

More information about the Interest mailing list