-
Notifications
You must be signed in to change notification settings - Fork 5.3k
Permit trailing data when parsing an X.509 certificate by DER content #82688
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
|
Tagging subscribers to this area: @dotnet/area-system-security, @vcsjones Issue DetailsThe managed X.509 decoder did not permit trailing data after the DER contents of the certificate. In #82682 it was reported that the Windows and Unix PALs permit this, so we should update the managed PAL to do the same. n.b. I generally liked the managed PAL's behavior here. We can't make Windows and Unix more strict without possibly breaking someone, but we can make the managed implementation more relaxed. Fixes #82682
|
|
/azp run runtime-ioslike runtime-android |
|
No pipelines are associated with this pull request. |
|
/azp help |
Supported commands
See additional documentation. |
|
/azp run runtime-ioslike, runtime-android |
|
Azure Pipelines successfully started running 2 pipeline(s). |
adamsitnik
left a comment
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, thank you @vcsjones !
The managed X.509 decoder did not permit trailing data after the DER contents of the certificate. In #82682 it was reported that the Windows and Unix implementations permit this, so we should update the managed PAL to do the same.
n.b. I generally liked the managed PAL's behavior here. We can't make Windows and Unix more strict without possibly breaking someone, but we can make the managed implementation more relaxed.
Fixes #82682