Since we got many reports starting from the November Patch Tuesday, it seems possible that something has changed, but I talked to someone in the Windows SCHANNEL team who confirmed with me that Windows does not and has never enabled TLS 1.3 by default. Since TLS 1.3 is enabled on Windows 10 via a registry key, and changes to the registry is not audited, it's impossible for us to know why so many customers started getting this problem. NET Core uses libssl, so whether it works there depends on if the libssl version supports TLS 1.3 and if so, if it implemented the lastest spec, or an earlier draft. ![]() However, TLS 1.3 in Windand earlier is not supported (I believe it implemeted an early draft of the TLS 1.3 spec, and was not updated when the spec changed, hence it's incompatible with some newer implementations). ![]() NET applications using HttpClient or HttpWebRequest will use it. Hence, when Windows is configured to used TLS1.3, all. ![]() NET uses Windows secure channel APIs to so TLS negotiation. The only root cause that we're aware of is on Windows 10 machines where TLS 1.3 was enabled in the registry. See this feedback on Visual Studio's Developer Community website, and/or this issue in the NuGetGallery () GitHub issue tracker.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |