That certainly fits with the scenario I’m seeing between Win 11 and Win 10 installations.
Looks like a libcurl update is in order for my software deployment. Thank you very much for helping to resolve this. Well done, Sir. Thanks, Dick Brooks Active Member of the CISA Critical Manufacturing Sector, Sector Coordinating Council – A Public-Private Partnership <https://reliableenergyanalytics.com/products> Never trust software, always verify and report! ™ Risk always exists, but trust must be earned and awarded.™ https://businesscyberguardian.com/ Email: d...@businesscyberguardian.com Tel: +1 978-696-1788 From: curl-users <curl-users-boun...@lists.haxx.se> On Behalf Of Ray Satiro via curl-users Sent: Saturday, December 28, 2024 4:32 PM To: curl-users@lists.haxx.se Cc: Ray Satiro <raysat...@yahoo.com> Subject: Re: Strange behavior processing SSL certs between a Windows 11 system running Python 3.13.1 and a Windows 10 system running Python 3.8.5 On 12/28/2024 4:27 PM, Dick Brooks via curl-users wrote: Looks like the libcurl version may be a suspect in this odd behavior. It’s the first time I’ve seen this happen. libcurl-7.71.1 I just read the original bug report [1] and the situation is a little different than I had explained. What happened was Windows changed the order of certificates in Windows 11 22H2 and so libcurl had to adapt to that. In versions of libcurl with schannel prior to 8.3.0 you may see a different certificate ordering depending on which version of Windows you are using. [1]: https://github.com/curl/curl/issues/9706
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-users Etiquette: https://curl.se/mail/etiquette.html
