On 18/08/2025 09.02, Stefan Weil wrote:
Am 18.08.25 um 07:49 schrieb Thomas Huth:
I'll queue your patch for my next pull request ... just wondering: Did you
run into any real issue here? AFAIK we're not running any related test on
Windows in the CI, so there should not be any big difference?
Hi,
HTTPS connections don't work unless the server certificate can be validated.
Binaries with mingw-w64-x86_64-curl won't find the common CA certificates,
so server certificates cannot be validated and HTTPS connections fail.
With mingw-w64-x86_64-curl-winssl, the installed CA certificates from
Windows are used and HTTPS works fine.
The difference is therefore for any protocol which uses SSL.
Sure, but I was just wondering whether you observed a failure in a CI job.
AFAIK we don't run any QEMU binary in that CI job, so the CI job itself
should not hit the problem. And we don't publish the binaries as artifacts
of the job either, so there's also no user that could run into this problem
with the generated binaries there.
But anyway, it's better to fix it, in case someone uses the list in the yml
file for their local installation to build QEMU, or in case we ever decide
to publish the binaries from the CI job for consumption by the users.
Thomas
