mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

idea, not impementing today

Browse source
This commit is contained in:
Joey Hess 2020-02-26 18:38:12 -04:00
parent 535ad3ba75
commit ce8a034ecd
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 21 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

21
doc/bugs/gcrypt_special_remote_not_working/comment_4_2fe8b29a06bac1e004f8fa2109a27fab._comment Normal file
View file

@ -0,0 +1,21 @@
[[!comment format=mdwn
username="joey"
subject="""comment 4"""
date="2020-02-26T22:34:35Z"
content="""
Hmm, one idea is that git-annex fsck --from remote, when the remote is
encrypted, could check if the non-encrypted key is present. If so, it
could warn loudly.
(I don't think it could delete it safely; the user would still have to do
that. Deleting it might violate numcopies and lead to data loss. It
could move it to the local repo, but that risks fsck filling up the local
repo, and also it's not guaranteed that the local repo is a place the user
expects to continue storing data; it could even be a throwaway repo they're
going to nuke after the fsck.)
This does make a slow fsck path even slower, which is a bit of a heavy
price to pay going forward. Although the belt-and-suspenders nature
of checking that git-annex has not forgotten to encrypt some data may be
worth it.
"""]]