Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release/6.0] improve SslStream tests on misconfigured systems #65024

Merged
merged 2 commits into from
Mar 11, 2022

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Feb 8, 2022

Backport of #64966 to release/6.0

/cc @safern @wfurt

Fixes #64943

Customer Impact

Testing

Risk

@ghost
Copy link

ghost commented Feb 8, 2022

Tagging subscribers to this area: @dotnet/ncl, @vcsjones
See info in area-owners.md if you want to be subscribed.

Issue Details

Backport of #64966 to release/6.0

/cc @safern @wfurt

Customer Impact

Testing

Risk

Author: github-actions[bot]
Assignees: -
Labels:

area-System.Net.Security

Milestone: -

@ericstj
Copy link
Member

ericstj commented Mar 11, 2022

@wfurt is this ready to be merged? Can we get fresh PR validation results and a signoff?

@ericstj
Copy link
Member

ericstj commented Mar 11, 2022

/azp run runtime

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@carlossanlop
Copy link
Member

In the main PR, we had this conversation:

wfurt: "safern we should take this to 6.0 if we ever back-port the 2022 queue."

safern: "We already did. So maybe we should get the backport going."

I think we should take this. @dotnet/ncl I don't see a sign-off from area owners but I'll sign it off myself this time. The CI is passing and it's a test only change, so it does not need the servicing-approved label.

@carlossanlop carlossanlop merged commit d0c82a3 into release/6.0 Mar 11, 2022
@carlossanlop carlossanlop deleted the backport/pr-64966-to-release/6.0 branch March 11, 2022 20:02
@karelz karelz added this to the 6.0.x milestone Apr 8, 2022
@ghost ghost locked as resolved and limited conversation to collaborators May 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants