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

Added a comment

Browse source
This commit is contained in:
interfect@b151490178830f44348aa57b77ad58c7d18e8fe7 2017-06-09 01:40:01 +00:00 committed by admin
parent 855f35d00d
commit e19752a653
1 changed files with 17 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
doc/bugs/Hybrid_encryption_can__39__t_generate_the_right_key_after_moving_files/comment_3_414bd487619e46b25e8d9a57d9aef1f6._comment Normal file
View file

@ -0,0 +1,17 @@
[[!comment format=mdwn
username="interfect@b151490178830f44348aa57b77ad58c7d18e8fe7"
nickname="interfect"
avatar="http://cdn.libravatar.org/avatar/3ba541a3204f4ea4b274049a152489c5"
subject="comment 3"
date="2017-06-09T01:40:00Z"
content="""
Unfortunately even though the content is still over at Amazon, ACD can no longer be accessed through rclone, so I can't get Git Annex to go over there and download it.
With the new chunk-supporting decryption script (which I further modified to actually use the timestamps on the log entries), I am able to generate the right key for my test file. I was also able to generate the key for and decrypt another test file, and then testing with git annex again shows that I can successfully fsck other file in the remote.
I think what is happening is that my small file I was testing with somehow became corrupted or was modified while on Amazon's servers. I downloaded from Amazon before the transfer and from Google after and did a diff, and both files are identical, so I think I moved over corrupt data.
It looks like git annex is just successfully doing its job and identifying some data corruption here. The bug can probably be closed.
"""]]