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

respinse

Browse source
This commit is contained in:
Joey Hess 2016-05-03 14:01:07 -04:00
parent 667376024c
commit debf582ae2
Failed to extract signature
1 changed files with 15 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
doc/devblog/day_387__release_day/comment_2_86262439c9056c0e06623cdf79eaf9a6._comment Normal file
View file

@ -0,0 +1,15 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2016-05-03T17:56:44Z"
content="""
The exposed information is not stored in the remote. If it's stored
anywhere, it would be in a server log, which might log an attempt
to access an un-encrypted key filename (which typically includes the
checksum and maybe the file's extension).
So on the one hand, you don't need to do anything other than upgrade
git-annex to recover from the problem. On the other hand, if the potential
that a un-encrypted filename of a git-annex key having leaked into a server
log somewhere is a problem, I don't have a solution to the problem. :-/
"""]]