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

Added a comment

Browse source
This commit is contained in:
nobodyinperson 2023-01-02 22:58:08 +00:00 • committed by admin
parent 6964b193f3
commit 45e71edc17
1 changed files with 14 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

14
doc/todo/encrypted_keys_in_git_repository/comment_5_05b0e2e88b233691b403d4c908b50c52._comment Normal file
View file

@ -0,0 +1,14 @@
[[!comment format=mdwn
username="nobodyinperson"
avatar="http://cdn.libravatar.org/avatar/736a41cd4988ede057bae805d000f4f5"
subject="comment 5"
date="2023-01-02T22:58:08Z"
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.
Ah alright, in that case scrypt doesn't help, I agree. Among the large userbase for such a versatile software as git-annex there surely are people that could make use of hiding the presence of some 'common' files from their public repos. Though it rather seems like quite an edge case to me 😅 Better go full-gcrypt in that case I'd say...
> sha2 is equally good protection as scrypt
In that case, this'll be enough for my application, thanks! 🙏
"""]]