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

updates

Browse source
This commit is contained in:
Joey Hess 2017-02-24 00:28:15 -04:00
parent 969da82b5c
commit 4cad401629
No known key found for this signature in database
GPG key ID: C910D9222512E3C7
2 changed files with 10 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

8
doc/devblog/day_449__SHA1_break_day.mdwn
View file

@ -11,9 +11,11 @@ Projects that store binary files in git, that might be worth $100k for an
attacker to backdoor **should** be concerned by the SHA1 collisions. attacker to backdoor **should** be concerned by the SHA1 collisions.
A good example of such a project is A good example of such a project is
<git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git>. <git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git>.
Using git-annex (with a suitable backend like SHA256) and signed commits Using git-annex (with a suitable backend like SHA256) and signed commits
together is a good way to secure such repositories. together is a good way to secure such repositories.
git-annex's SHA1 backend is already documented as only being Update 12:25 am: However, there are some ways to embed SHA1-colliding data
"for those who want a checksum but are not concerned about in the names of git-annex keys. That makes git-annex with signed
security", so no changes needed here. commits be no more secure than git with signed commits. I am working
to fix git-annex to not use keys that have such problems.

4
doc/todo/sha1_collision_embedding_in_git-annex_keys.mdwn
View file

@ -30,5 +30,7 @@ A few other potential problems:
* It might be possible to embed colliding data in a specially constructed * It might be possible to embed colliding data in a specially constructed
key name with an extra field in it, eg "SHA256-cXXXXXXXXXXXXXXX-...". key name with an extra field in it, eg "SHA256-cXXXXXXXXXXXXXXX-...".
Need to review the code and see if such extra fields are allowed. Need to review the code and see if such extra fields are allowed.
Update: All fields are numeric, but could contain arbitrary data Update: All fields are numeric, but could contain arbitrary data
after the number. (fixed now) after the number. This has been fixed; git-annex refuses to parse
such fields, so it won't work with files that try to exploit this.