Report path to missing internal key#22
Open
pjungwir wants to merge 1 commit into
Open
Conversation
This is helpful if we fail while looking for the key in its default location.
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.
Thank you for continuing to maintain this project!
I had a repo I started with git-crypt in 2018, and after some OS upgrades
git statusstarted to fail with this cryptic error:My gpg key was still there, so I didn't know what the problem was. Finally I looked at the gpg-crypt source code, and there was already a TODO comment to report the path to the missing key. Here is a PR adding that.
Once I made this change, I could see that it was looking for
.git/common/git-crypt/git-crypt/keys/default. Instead I had.git/git-crypt/keys/default. So after this my repo worked again!: