re-enable TLS 13 tests on Windows #68009
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Tagging subscribers to this area: @dotnet/ncl, @vcsjones Issue DetailsWhile the underlying issue lives in Schannel and it is being fixed in Windows the root analyses points to certificates with CAPI provider. That works fine for previous TLS versions but it fails for TLS 1.3 as that is somehow different. This change brings new pfx files from dotnet/runtime-assets#234 This is only fix for the other (recent server 2022) failures are unrelated to this. fixes #58927
|
This was referenced Apr 14, 2022
Closed
|
/azp run runtime-extra-platforms |
|
Azure Pipelines successfully started running 1 pipeline(s). |
ghost
locked as resolved and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While the underlying issue lives in Schannel and it is being fixed in Windows the root analyses points to certificates with CAPI provider. That works fine for previous TLS versions but it fails for TLS 1.3 as that is somehow different.
This change brings new pfx files from dotnet/runtime-assets#234
With updated data (essentially still same certificate) everything seems to be stable.
This is only fix for the
other (recent server 2022) failures are unrelated to this.
fixes #58927