diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2017-02-24 00:28:15 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2017-02-24 00:28:15 -0400 |
| commit | ef24392f8488cf3649c422eeab614a056d89d2d0 (patch) | |
| tree | 0d382b36ca734691caa57e90a1fa42914b0b117b /doc/todo | |
| parent | 7c97656dda76c83383554005bd0f7b5e24993efa (diff) | |
updates
Diffstat (limited to 'doc/todo')
| -rw-r--r-- | doc/todo/sha1_collision_embedding_in_git-annex_keys.mdwn | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/todo/sha1_collision_embedding_in_git-annex_keys.mdwn b/doc/todo/sha1_collision_embedding_in_git-annex_keys.mdwn index 7acbfde13..dc3dccdc5 100644 --- a/doc/todo/sha1_collision_embedding_in_git-annex_keys.mdwn +++ b/doc/todo/sha1_collision_embedding_in_git-annex_keys.mdwn @@ -30,5 +30,7 @@ A few other potential problems: * It might be possible to embed colliding data in a specially constructed key name with an extra field in it, eg "SHA256-cXXXXXXXXXXXXXXX-...". Need to review the code and see if such extra fields are allowed. + 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. |