-
-
Notifications
You must be signed in to change notification settings - Fork 337
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
SSH Permission Changes #185
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.
Thanks for opening this pull request! Be sure to follow the pull request template!
I am a bot, here are the test results for this PR:
|
I am a bot, here are the test results for this PR:
|
I am a bot, here are the test results for this PR:
|
PR looks excellent, thanks @markagonzales - just run into this issue myself and I'm currently working around it with Thanks! |
Could you update the changelog date and then I'm happy to merge this |
I am a bot, here are the test results for this PR:
|
Description:
This PR changes how
code-server
manages files in the/config/.ssh
directory on startup. Three scoped find commands replace the existingchown
and enforces the correct file permission for directories, private keys, and public keys that may be present.Benefits of this PR and context:
The
.ssh
can have other files in that directory which the current. Although it addresses unsafe permissions and satisfies the client, the current behavior over corrects what those permissions should be and potentially disrupt how that directory is organized.How Has This Been Tested?
A nod to the recommendation to NOT mount into an existing mount path but for testing purposes...
Subdirectories should remain user at least 700, public keys should have 644 permissions, and private keys 600.
Source / References: