-
Notifications
You must be signed in to change notification settings - Fork 796
dotnet: improve dev-certs instructions #1095
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
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.
Looks good, left one comment.
Co-authored-by: Samruddhi Khandale <samruddhikhandale@github.com>
|
Thanks for the reviews @samruddhikhandale @chrmarti I applied the suggestions. Can you review again? |
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.
Appreciate the doc update, thanks!
I updated the README for dotnet with a better way to manage HTTPS development certificates for ASP.NET Core.
Previously, it recommended a solution that did not work well in team or open source environments, as it required manual steps, and the solution carried a risk of unintended password disclosure.
I added a solution which does not require manual steps, nor does it have any risk of leaking passwords.
I did not remove the old instructions, but I did add a warning to avoid using it for shared projects.