Details
-
Bug
-
Resolution: Done
-
P2: Important
-
None
-
5.13.2, 5.14.0, 5.15.0, 5.15.2
-
None
-
msvc2017_64, msvc2019_64
-
Windows
Description
The opengl32sw.dll binary included in the Qt 5.13.2 msvc2017_64 distribution seem to lack a cryptographic signature, whereas all other binaries (that I've checked) are signed by either Microsoft of the Qt Company. As a consequence of this, Windows 10 Device Guard might be blocking startup of our Qt-based applications.
We currently work around this issue by modifying opengl32sw.dll ourselves by applying our own signature. However, relying on custom modifications to the Qt SDK isn't really a good long-term solution.
Attachments
| For Gerrit Dashboard: QTBUG-80252 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 302941,2 | Provisioning: Use signed opengl32 package | dev | qt/qt5 | Status: MERGED | +2 | 0 |
| 303199,6 | Provisioning: Use signed opengl32 package | 5.15 | qt/qt5 | Status: MERGED | +2 | 0 |
| 303633,2 | Provisioning: Use signed opengl32 package | 5.12 | qt/qt5 | Status: MERGED | +2 | 0 |
| 332940,1 | Start using signed opengl32sw.dll in Qt 5.12 and Qt 5.15 LTS | master | qtsdk/tqtc-qtsdk | Status: ABANDONED | +1 | 0 |