Breaking Change: Removal of ASP.NET Core Developer Certificate #933
mthalman
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Breaking Change: Removal of ASP.NET Core Developer Certificate
The ASP.NET Core self-signed developer certificate will no longer be included in
sdk
Docker images, starting with the next servicing release on August 10, 2021. This applies to all supportedsdk
images because they contain an installation of .NET 5.0.This should be considered a breaking change but is unlikely to affect many people. If you're dependent on this certificate existing in the
sdk
image, you should follow the steps below to avoid being affected by the upcoming release.Details
The inclusion of this certificate is an oversight as it is against our policy to distribute self-signed certificates. Distributing a certificate in this manner allows it to be misused by malicious actors, potentially allowing users who have trusted the self-signed certificate to fall victim to spoofing attacks. However, given that the certificate is signed as localhost, the likelihood of this occurring in a real-world situation is low.
Recommended Action
Rather than relying on a self-signed certificate already existing in the container, the recommended pattern is to generate the certificate on the host machine and volume mount the certificate into the container. Please read through the existing documentation on how to do this.
Cleanup of Trusted Certificate
If you installed the ASP.NET Core developer certificate described above as a trusted certificate on another machine (outside of the container), it is recommended that you remove this certificate. The PowerShell script provided below, compatible with Windows and MacOS, can be executed to remove the certificate:
Beta Was this translation helpful? Give feedback.
All reactions