diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2017-02-24 20:03:36 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2017-02-24 20:03:36 -0400 |
| commit | 3e28f10759a3f6e7a5cf947db0c975b70151e6f7 (patch) | |
| tree | 6d8ba118814e76d28cfb12d7f08e59db914c148d /doc/devblog | |
| parent | a091af71fc8161427f8d9553042d0bc41507fff7 (diff) | |
devblog
Diffstat (limited to 'doc/devblog')
| -rw-r--r-- | doc/devblog/day_450__hardening_against_SHA_attacks.mdwn | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/doc/devblog/day_450__hardening_against_SHA_attacks.mdwn b/doc/devblog/day_450__hardening_against_SHA_attacks.mdwn new file mode 100644 index 000000000..5e419dea7 --- /dev/null +++ b/doc/devblog/day_450__hardening_against_SHA_attacks.mdwn @@ -0,0 +1,13 @@ +Yesterday I said that a git-annex repository using signed commits and SHA2 +backend would be secure from SHA1 collision attacks. Then I noticed that +there were two ways to embed the necessary collision generation data inside +git-annex key names. I've fixed both of them today, and cannot find any +other ways to embed collision generation data in between a signed commit +and the annexed files. + +I also have a design for a way to configure git-annex to expect to see only +keys using secure hash backends, which will make it easier to work with +repositories that want to use signed commits and SHA2. Planning to implement +that tomorrow. + +[[todo/sha1_collision_embedding_in_git-annex_keys]] has the details. |