mtoohey31/git-crypt-agessh

Encrypt files in git using age and ed25519 ssh keys.

git-crypt-agessh's Issues

Decryption when checking the previous version should be allowed to fail

There's no guarantee that the current host will have been a recipient in the previous version, and in fact, no requirement that it must be a recipient in the current version either, so we should allow decryption to fail when comparing the current text to the previous version. If it does fail, we should re-encrypt.

Git thinks encrypted files have been modified when they aren't

Even with the check comparing the current text to the previous encrypted text, git still often thinks encrypted files have been changed when they haven't been. If we can determine under what circumstances this occurs, we could probably fix this by using the go-git equivalent of git update-index --assume-unchanged when the clean/smudge filters realize this situation is about to occur.

Updating recipients without updating file doesn't work properly

If the recipients for an encrypted file are updated without the file itself being changed, the value checking logic in the clean subcommand won't update the file, it'll reuse the old version. Normally reusing the old version is correct, but not when we update the recipients, so when we compare against the old version, we also need to compare the recipients for the old version with the recipients for the new version, because if those are different then we also need to re-encrypt.

Move recipient declaration from comment to git attribute