diff options
| author | Sebastian Reuße <seb@wirrsal.net> | 2017-01-25 09:14:42 +0100 |
|---|---|---|
| committer | Jason A. Donenfeld <Jason@zx2c4.com> | 2017-02-25 13:40:03 +0100 |
| commit | be6cebe0df6d9ff0f67bd50cf96a5faaac00416c (patch) | |
| tree | 377354c6dc3f8f46c24bcb317a13b370aa7f5971 /tests/gnupg/private-keys-v1.d | |
| parent | 3691b66a31266b83b0b047ee955139cdb91f3ede (diff) | |
| download | pass-be6cebe0df6d9ff0f67bd50cf96a5faaac00416c.tar.gz pass-be6cebe0df6d9ff0f67bd50cf96a5faaac00416c.tar.bz2 pass-be6cebe0df6d9ff0f67bd50cf96a5faaac00416c.zip | |
Don’t reencrypt data not managed by pass.
When keeping the password-store under git, it can make sense using a git
extension such as git-annex instead of the native git object store to
store the encrypted files. Inter alia, this allows one to selectively
expire old copies of the encrypted data, while otherwise, one would need
to recreate the complete repository when a key should no longer have
access to some of the data.
Since using the git-annex object store means that *.gpg files (and
directories named *.gpg) are kept under .git/… (non-writable), the
reencryption logic used by pass currently fails. To remedy this, we now
ignore everything kept under .git when looking for files to reencrypt or
when grepping.
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions