Skip to content

[Platform] Detect and fix certificates with potentially inaccessible keys on Mac OS (3.0) #17580

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 3 commits into from
Jan 16, 2020

Conversation

javiercn
Copy link
Member

@javiercn javiercn commented Dec 4, 2019

Description

We are signing the SDK installer and packages for Mac OS Catalina compliance with the requirement to have packages notarized. That change affects the way HTTPS works in ASP.NET Core and prevents users from running their ASP.NET Core applications.

To mitigate the issue we are including logic in Kestrel that detects this situation and informs customers of what steps to take to mitigate the issue and we are updating the "dotnet dev-certs" tool to detect when this situation can happen and to fix it automatically when the "dotnet dev-certs https" command is run.

Customer Impact

High

Once a customer installs an updated SDK version they won't be able to run their applications normally unless they fix the existing certificate.

Regression?

No, this is a new requirement introduced by Mac OS Catalina.

Risk

Low, the runtime changes are already present in 3.1 and the changes on the tool are simple.

Implementation details

  • This is just a port of the 3.1 and 2.1 fixes (runtime and tool) respectively.

…ate can't be used (#16659)

Improves the error message Kestrel gives when the developer certificate key is not available for some reason.
@javiercn javiercn requested a review from Pilchie December 4, 2019 13:04
@javiercn javiercn added the feature-platform Deprecated: Cross-cutting issues related to ASP.NET Core as a platform label Dec 4, 2019
@javiercn javiercn force-pushed the javiercn/https-mac-os-30 branch from a97f7f6 to 9c989c5 Compare December 4, 2019 16:31
@javiercn javiercn marked this pull request as ready for review December 4, 2019 16:50
@javiercn
Copy link
Member Author

javiercn commented Dec 4, 2019

@aspnet/build There seems to be an issue here with the builds on the CI not even starting

@javiercn javiercn added the Servicing-consider Shiproom approval is required for the issue label Dec 4, 2019
@pranavkm
Copy link
Contributor

pranavkm commented Dec 4, 2019

@mkArtakMSFT mkArtakMSFT added this to the 3.0.x milestone Dec 5, 2019
@jamshedd jamshedd added Servicing-approved Shiproom has approved the issue and removed Servicing-consider Shiproom approval is required for the issue labels Dec 10, 2019
@jamshedd jamshedd modified the milestones: 3.0.x, 3.0.3 Dec 10, 2019
@javiercn
Copy link
Member Author

/AzurePipelines run AspNetCore-ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@javiercn
Copy link
Member Author

/AzurePipelines run AspNetCore-ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@dougbu
Copy link
Contributor

dougbu commented Jan 16, 2020

All required tests passing. @javiercn @mkArtakMSFT are we waiting for anything here?

@mkArtakMSFT mkArtakMSFT merged commit bba3430 into release/3.0 Jan 16, 2020
@mkArtakMSFT mkArtakMSFT deleted the javiercn/https-mac-os-30 branch January 16, 2020 06:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-platform Deprecated: Cross-cutting issues related to ASP.NET Core as a platform Servicing-approved Shiproom has approved the issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants