Skip to content

Use X509Certificate2 constructor instead of Import (SYSLIB0026) #9807

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

Merged
merged 1 commit into from
May 3, 2024

Conversation

MiguelDomingues
Copy link
Contributor

Summary

Import is marked as obsolete (SYSLIB0026):

'X509Certificate.Import(byte[])' is obsolete: 'X509Certificate and X509Certificate2 are immutable. Use the appropriate constructor to create a new certificate.'

@MiguelDomingues MiguelDomingues requested a review from a team as a code owner April 12, 2024 11:13
@ghost ghost added the area-System.Security Issues related to security practices for .NET developers. label Apr 12, 2024
@dotnet-policy-service dotnet-policy-service bot added the community-contribution Indicates that the PR has been added by a community member label Apr 12, 2024
Copy link
Contributor

Tagging subscribers to this area: @dotnet/area-system-security, @vcsjones

@gewarren gewarren closed this May 3, 2024
@gewarren gewarren reopened this May 3, 2024
@gewarren gewarren enabled auto-merge (squash) May 3, 2024 17:48
Copy link

Learn Build status updates of commit 2cae909:

✅ Validation status: passed

File Status Preview URL Details
snippets/csharp/System.Security.Cryptography.X509Certificates/PublicKey/Overview/certinfo.cs ✅Succeeded View

For more details, please refer to the build report.

For any questions, please:

@gewarren gewarren merged commit eb7588a into dotnet:main May 3, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-System.Security Issues related to security practices for .NET developers. community-contribution Indicates that the PR has been added by a community member
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants