fix(git-commit-signing): fix SSH key permissions #152
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
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.
Closes #149.
in Linux it's fine to modify a file's permissions that only has read permissions if you're the owner, but you still can't write to them, so if the home folder of the user is persisted, then it'll cause issues on every startup, this PR makes the files writable by the owner.
~/.ssh/git-commit-signing/codergoes from400to600~/.ssh/git-commit-signing/coder.pubgoes from400to644these are the default values when using
ssh-keygen, I don't know why I didn't use those permissions when writing the script.