This is a minor correction for the dev-cert instructions that I added earlier this week in #1095.
In the original instructions, sudo is used to generate a new dev-cert. As a result, the vscode user might be unable to use the dev-cert due to insufficient permissions. The dev-cert is owned by root:root and the file permissions are -rw------ (600).
The solution is simply to run the dotnet dev-certs https command first as the vscode user, resulting in the file being created with correct ownership. The use of sudo is still needed to export the dev-cert to the ca-certificates/ directory.
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.