February 2026 - Wine-GitLab

[PATCH v4 0/1] MR10174: bcryptprimitives: Abort if ProcessPrng fails
by Christopher Denton (＠cdenton) Feb. 24, 2026

Feb. 24, 2026

[`ProcessPrng`] is documented as always returning TRUE. So I've modified `ProcessPrng` to abort on errors. This is I believe an import aspect of the function. See Microsoft's [The Windows 10 random number generation infrastructure] whitepaper. > We also have the property that a request for random bytes never fails. In the past our RNG functions could return an error code. We have observed that there are many callers that never check for the error code, even if they are generating cryptographic key material. This can lead to serious security vulnerabilities if an attacker manages to create a situation in which the RNG infrastructure returns an error. For that reason, the Win10 RNG infrastructure will never return an error code and always produce high-quality random bytes for every request. [`ProcessPrng`]: https://learn.microsoft.com/en-us/windows/win32/seccng/processprng [The Windows 10 random number generation infrastructure]: https://www.microsoft.com/en-us/security/blog/2019/11/25/going-in-depth-on-… -- v4: bcryptprimitives: Abort if ProcessPrng fails https://gitlab.winehq.org/wine/wine/-/merge_requests/10174

3 2

[PATCH v3 0/1] MR10174: bcryptprimitives: Abort if ProcessPrng fails
by Christopher Denton (＠cdenton) Feb. 24, 2026

Feb. 24, 2026

[`ProcessPrng`] is documented as always returning TRUE. So I've modified `ProcessPrng` to abort on errors. This is I believe an import aspect of the function. See Microsoft's [The Windows 10 random number generation infrastructure] whitepaper. > We also have the property that a request for random bytes never fails. In the past our RNG functions could return an error code. We have observed that there are many callers that never check for the error code, even if they are generating cryptographic key material. This can lead to serious security vulnerabilities if an attacker manages to create a situation in which the RNG infrastructure returns an error. For that reason, the Win10 RNG infrastructure will never return an error code and always produce high-quality random bytes for every request. [`ProcessPrng`]: https://learn.microsoft.com/en-us/windows/win32/seccng/processprng [The Windows 10 random number generation infrastructure]: https://www.microsoft.com/en-us/security/blog/2019/11/25/going-in-depth-on-… -- v3: bcryptprimitives: Abort if ProcessPrng fails https://gitlab.winehq.org/wine/wine/-/merge_requests/10174

1 0

[PATCH v2 0/1] MR10174: bcryptprimitives: Abort if ProcessPrng fails
by Christopher Denton (＠cdenton) Feb. 24, 2026

Feb. 24, 2026

[`ProcessPrng`] is documented as always returning TRUE. So I've modified `ProcessPrng` to abort on errors. This is I believe an import aspect of the function. See Microsoft's [The Windows 10 random number generation infrastructure] whitepaper. > We also have the property that a request for random bytes never fails. In the past our RNG functions could return an error code. We have observed that there are many callers that never check for the error code, even if they are generating cryptographic key material. This can lead to serious security vulnerabilities if an attacker manages to create a situation in which the RNG infrastructure returns an error. For that reason, the Win10 RNG infrastructure will never return an error code and always produce high-quality random bytes for every request. [`ProcessPrng`]: https://learn.microsoft.com/en-us/windows/win32/seccng/processprng [The Windows 10 random number generation infrastructure]: https://www.microsoft.com/en-us/security/blog/2019/11/25/going-in-depth-on-… -- v2: bcryptprimitives: Abort if ProcessPrng fails https://gitlab.winehq.org/wine/wine/-/merge_requests/10174

4 7

[PATCH 0/1] MR10178: compiler-rt: add __ctzdi2 to fix i386 mingw builds
by Maotong Zhang (＠xiaotong) Feb. 24, 2026

Feb. 24, 2026

Commit 8d8d871b switched mingw from -lgcc to compiler-rt. This breaks i386 builds with ccache: Capstone fails to link (AArch64/ARM disassemblers) due to an undefined __ctzdi2 symbol. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10178

2 1

[PATCH 0/1] MR10177: ntdll: Fix threadpool timer behavior on system time change.
by Piotr Caban (＠piotr) Feb. 24, 2026

Feb. 24, 2026

Threadpool timers are not handling system clock changes correctly. Observed while trying to start delayed-start service on DST change (service started after 1h02m instead of 2m). These patch changes threadpool timers to use NtCreateTimers internally. It matches with native implementation as documented here: https://github.com/SafeBreach-Labs/PoolParty. While it moves implementation closer to what native does I didn't work on making it binary compatible. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10177

1 0

[PATCH v2 0/3] MR10175: winmm/tests: Test a curated list of wave formats.
by Giovanni Mascellani (＠giomasce) Feb. 24, 2026

Feb. 24, 2026

This has of course a lot of code in common with the mmdevapi tests, but I don't know what would be a good place to share it. Happy to take suggestions. -- v2: winmm/tests: Test a curated list of wave formats. https://gitlab.winehq.org/wine/wine/-/merge_requests/10175

2 3

[PATCH 0/3] MR10176: cfgmgr32/tests: Tweak the test results for some testbot VMs.
by Rémi Bernon Feb. 24, 2026

Feb. 24, 2026

-- https://gitlab.winehq.org/wine/wine/-/merge_requests/10176

1 0

[PATCH 0/1] MR9988: msvcrt time: add overflow checks for avoiding year 2038 problem
by Herman Semenov (＠GermanAizek) Feb. 24, 2026

Feb. 24, 2026

There have already been type overflow checks in same code time.c, but they are not enough. https://gitlab.winehq.org/wine/wine/-/blob/master/dlls/msvcrt/time.c#L336-3… References: - https://en.wikipedia.org/wiki/Year_2038_problem - https://www.gnu.org/software/gnulib/manual/html_node/Avoiding-the-year-2038… -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9988

3 5

[PATCH 0/1] MR10174: bcryptprimitives: Abort if ProcessPrng fails
by Christopher Denton (＠cdenton) Feb. 24, 2026

Feb. 24, 2026

[`ProcessPrng`] is documented as always returning TRUE. So I've modified `ProcessPrng` to abort on errors. This is I believe an import aspect of the function. See Microsoft's [The Windows 10 random number generation infrastructure] whitepaper. > We also have the property that a request for random bytes never fails. In the past our RNG functions could return an error code. We have observed that there are many callers that never check for the error code, even if they are generating cryptographic key material. This can lead to serious security vulnerabilities if an attacker manages to create a situation in which the RNG infrastructure returns an error. For that reason, the Win10 RNG infrastructure will never return an error code and always produce high-quality random bytes for every request. [`ProcessPrng`]: https://learn.microsoft.com/en-us/windows/win32/seccng/processprng [The Windows 10 random number generation infrastructure]: https://www.microsoft.com/en-us/security/blog/2019/11/25/going-in-depth-on-… -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10174

2 2

[PATCH 0/3] MR10175: winmm/tests: Test a curated list of wave formats.
by Giovanni Mascellani (＠giomasce) Feb. 24, 2026

Feb. 24, 2026

This has of course a lot of code in common with the mmdevapi tests, but I don't know what would be a good place to share it. Happy to take suggestions. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10175

2 3