Overview
Request 945907 accepted
Add bug references so we don't miss them when updating Qt in SLE/Leap
* Fallback to /tmp/runtime-$USER if XDG_RUNTIME_DIR is not set
or is unsafe (bsc#1172515)
* Fixes CVE-2020-17507, bsc#1176315
* Qt incorrectly calls SSL_shutdown() in OpenSSL mid-handshake
causing denial of service in TLS applications (bsc#1172726,
CVE-2020-13962, QTBUG-83450)
* Fixes CVE-2020-0570, bsc#1161167, bsc#1162191, QTBUG-81272
* Fix segfaults due to unaligned stack in QtCore5 (bsc#1155955)
* Add support for PostgreSQL 12 (bsc#1173758)
* Qt headers redefine opengl types differently than khronos headers
(bsc#1176130)
Request History
alarrosa created request
Add bug references so we don't miss them when updating Qt in SLE/Leap
* Fallback to /tmp/runtime-$USER if XDG_RUNTIME_DIR is not set
or is unsafe (bsc#1172515)
* Fixes CVE-2020-17507, bsc#1176315
* Qt incorrectly calls SSL_shutdown() in OpenSSL mid-handshake
causing denial of service in TLS applications (bsc#1172726,
CVE-2020-13962, QTBUG-83450)
* Fixes CVE-2020-0570, bsc#1161167, bsc#1162191, QTBUG-81272
* Fix segfaults due to unaligned stack in QtCore5 (bsc#1155955)
* Add support for PostgreSQL 12 (bsc#1173758)
* Qt headers redefine opengl types differently than khronos headers
(bsc#1176130)
cgiboudeaux accepted request
Is there a particular reason for boo#1176130 to be private?
Not at all. I don't know why it's private. It's something quite "trivial" (the fix was submitted at https://build.opensuse.org/request/show/831665) so I'll try to make it public
@cgiboudeaux unfortunately anything reported as a SLE bug is made private and is hard to make un private in the current setup. Its something i'd still like to see changed.
It seems the reason is that I reported it against SLES which makes it private (btw, I reported it and also assigned it to me) and it seems it's not easy to make it public now. I'll add you to CC to see if that helps at least so you can see it. In any case, just for reference, the title is "Qt headers redefine opengl types differently than khronos headers" and the fix is open and can be seen in the SR mentioned in the other comment.
ok, let's see if that passes the factory review without a new changelog entry (I don't think)