-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Dead end S.Security.Cryptography.OpenSsl package #51854
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
Conversation
To reduce complexity of the cryptography OpenSsl library, dead ending its package as most of the configurations are partial facades anyway and adding OpenSsl to the targeting pack. It's already part of the runtime and exposed in aspnetcore's targeting pack. .NET Standard libraries can continue to use the latest available package which harvests for .NET Standard configurations. Contributes to dotnet#47530
Tagging subscribers to this area: @bartonjs, @vcsjones, @krwq, @GrabYourPitchforks Issue DetailsTo reduce complexity of the cryptography OpenSsl library, dead ending .NET Standard libraries can continue to use the latest available package Contributes to #47530
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM modulo the cleanup that @bartonjs might want to do.
To reduce complexity of the cryptography OpenSsl library, dead ending
its package as most of the configurations are partial facades anyway and
adding OpenSsl to the targeting pack. It's already part of the runtime
and exposed in aspnetcore's targeting pack. Note that the Platform
Analyzer will discourage the usage of these APIs on unsupported platforms.
.NET Standard libraries can continue to use the latest available package
which harvests for .NET Standard configurations.
Contributes to #47530