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] Update SAN test to account for OpenSSL 3 changes #63951

Merged
merged 2 commits into from
Feb 7, 2022

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jan 18, 2022

Backport of #63655 to release/6.0

/cc @bartonjs @vcsjones

Customer Impact

This is a test-only change.

Testing

This is a test-only change to account for increased support in OpenSSL 3.

Risk

Minimal (test-only change)

@ghost
Copy link

ghost commented Jan 18, 2022

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

Issue Details

Backport of #63655 to release/6.0

/cc @bartonjs @vcsjones

Customer Impact

Testing

Risk

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

area-System.Security

Milestone: -

@bartonjs bartonjs added the Servicing-consider Issue for next servicing release review label Jan 18, 2022
@akoeplinger
Copy link
Member

The test failure in runtime (Libraries Test Run release coreclr windows x64 Debug) is due to #63888

@danmoseley danmoseley removed the Servicing-consider Issue for next servicing release review label Jan 20, 2022
@danmoseley
Copy link
Member

No need for servicing-consider for tests only changes. @safern will handle merging though.

@safern safern merged commit 5efff44 into release/6.0 Feb 7, 2022
@safern safern deleted the backport/pr-63655-to-release/6.0 branch February 7, 2022 18:58
@ghost ghost locked as resolved and limited conversation to collaborators Mar 9, 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.

5 participants