Skip to content

Conversation

@vcsjones
Copy link
Member

This resolves two more unmapped chain status issues with macOS.

Fixes #35533
Fixes #35492

If a certificate contains an unprocessable critical extension
in a certificate, map the "CriticalExtensions" status to
HasNotSupportedCriticalExtension instead of throwing an exception.
X509Chain on Windows will not check for modern signatures, so we
will let macOS do the same thing.
@ghost
Copy link

ghost commented Apr 28, 2020

Tagging subscribers to this area: @bartonjs, @vcsjones, @krwq
Notify danmosemsft if you want to be subscribed.

@vcsjones
Copy link
Member Author

@bartonjs random thought: the unit tests written for these macOS cert building statuses make decent use of the CustomTrustStore, which is not in Core 3.1. The Basic Constraints PR kind of depends on it since OpenSSL doesn't check the path length for partial chains.

What's the best way to move forward with porting these fixes to corefx?

@bartonjs
Copy link
Member

The tests that can't be backported because they require new features can just be left out; and that'll just be a comment in the servicing paperwork.

@bartonjs bartonjs merged commit e301ec1 into dotnet:master Apr 28, 2020
@vcsjones vcsjones deleted the fix-35533-35492 branch April 28, 2020 14:19
@ghost ghost locked as resolved and limited conversation to collaborators Dec 9, 2020
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.

WeakSignature is not handled by X509 PAL on macOS Unknown CriticalExtensions is not handled by X509 PAL on macOS

3 participants