dotnet: amend dev-cert script in README #1103
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello again,
This is a minor correction for the dev-cert instructions that I added earlier this week in #1095.
In the original instructions,
sudois used to generate a new dev-cert. As a result, thevscodeuser might be unable to use the dev-cert due to insufficient permissions. The dev-cert is owned byroot:rootand the file permissions are-rw------(600).The solution is simply to run the
dotnet dev-certs httpscommand first as thevscodeuser, resulting in the file being created with correct ownership. The use ofsudois still needed to export the dev-cert to theca-certificates/directory.