update
This commit is contained in:
parent
8c9d9eb8af
commit
0d1f202334
1 changed files with 4 additions and 7 deletions
|
@ -78,13 +78,10 @@ keys.
|
||||||
|
|
||||||
## filename enumeration
|
## filename enumeration
|
||||||
|
|
||||||
If the names of files are encrypted, this makes it harder for
|
If the names of files are encrypted or securely hashed, or whatever is
|
||||||
git-annex (let alone untrusted third parties!) to get a list
|
chosen, this makes it harder for git-annex (let alone untrusted third parties!)
|
||||||
of the files that are stored on a given enrypted remote. This has been
|
to get a list of the files that are stored on a given enrypted remote.
|
||||||
a concern, and it has been considered to use a hash like HMAC, rather
|
But, does git-annex really ever need to do such an enumeration?
|
||||||
than gpg encrypting filenames, to make it easier. (For git-annex, but
|
|
||||||
possibly also for attackers!) But, does git-annex really ever need to do
|
|
||||||
such an enumeration?
|
|
||||||
|
|
||||||
Apparently not. `git annex unused --from remote` can now check for
|
Apparently not. `git annex unused --from remote` can now check for
|
||||||
unused data that is stored on a remote, and it does so based only on
|
unused data that is stored on a remote, and it does so based only on
|
||||||
|
|
Loading…
Reference in a new issue