comment
This commit is contained in:
parent
599758e0d3
commit
c326e5100f
1 changed files with 14 additions and 0 deletions
|
@ -0,0 +1,14 @@
|
||||||
|
[[!comment format=mdwn
|
||||||
|
username="joey"
|
||||||
|
subject="""comment 4"""
|
||||||
|
date="2023-01-02T19:03:34Z"
|
||||||
|
content="""
|
||||||
|
I'm talking about a single file that the attacker already knows the content
|
||||||
|
of, and wishes to determine if it's present in the repository. That takes a
|
||||||
|
single scrypt operation, so scrypt's added difficulty is not relevant.
|
||||||
|
|
||||||
|
If the attacker doesn't know the file content, and is trying to hash random
|
||||||
|
values until they find one that matches the git-annex key, then a sha2 is
|
||||||
|
equally good protection as scrypt, because the amount of work is
|
||||||
|
computationally infeasible in both cases.
|
||||||
|
"""]]
|
Loading…
Add table
Add a link
Reference in a new issue