Skip to content

Conversation

bartonjs
Copy link
Member

When used to describe the inputs to these methods, the references to Base64 really meant PEM, which utilizes Base64 within the encapsulation boundary.

There are still references to Base64 remaining, but they are used correctly, explaining PEM.

Fixes #10436

When used to describe the inputs to these methods, the references to Base64
really meant PEM, which utilizes Base64 within the encapsulation boundary.

There are still references to Base64 remaining, but they are used correctly,
explaining PEM.
@bartonjs bartonjs requested a review from a team as a code owner October 31, 2024 18:18
@ghost ghost added the area-System.Security Issues related to security practices for .NET developers. label Oct 31, 2024
Copy link
Contributor

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

Copy link

Learn Build status updates of commit 8d7bd3d:

✅ Validation status: passed

File Status Preview URL Details
xml/System.Security.Cryptography.X509Certificates/X509Certificate2.xml ✅Succeeded View

For more details, please refer to the build report.

For any questions, please:

@bartonjs bartonjs merged commit 50b38a0 into dotnet:main Oct 31, 2024
4 checks passed
@bartonjs bartonjs deleted the base64_meant_pem branch October 31, 2024 18:41
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

X509Certificate2 constructor remarks on acceptable data formats are incorrect
3 participants