File: comment_2_86262439c9056c0e06623cdf79eaf9a6._comment

package info (click to toggle)
git-annex 6.20170101-1%2Bdeb9u2
  • links: PTS
  • area: main
  • in suites: stretch
  • size: 50,088 kB
  • sloc: haskell: 53,116; sh: 1,582; ansic: 341; makefile: 292; perl: 144
file content (15 lines) | stat: -rw-r--r-- 651 bytes parent folder | download | duplicates (7) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
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. :-/
"""]]