diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2017-02-27 16:08:16 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2017-02-27 16:08:23 -0400 |
| commit | 025b8102e5741f437e970eb29593ced31b0554e4 (patch) | |
| tree | 9c6d4376dfd3740c4c0f902bae6015278b23d0b0 /doc/todo | |
| parent | acaaf842b5afbf3e6d0c0095cbe15699ab2419d3 (diff) | |
inheritable annex.securehashesonly
* init: When annex.securehashesonly has been set with git-annex config,
copy that value to the annex.securehashesonly git config.
* config --set: As well as setting value in git-annex branch,
set local gitconfig. This is needed especially for
annex.securehashesonly, which is read only from local gitconfig and not
the git-annex branch.
doc/todo/sha1_collision_embedding_in_git-annex_keys.mdwn has the
rationalle for doing it this way. There's no perfect solution; this
seems to be the least-bad one.
This commit was supported by the NSF-funded DataLad project.
Diffstat (limited to 'doc/todo')
| -rw-r--r-- | doc/todo/sha1_collision_embedding_in_git-annex_keys.mdwn | 5 |
1 files changed, 4 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 2f345a088..37da39a8d 100644 --- a/doc/todo/sha1_collision_embedding_in_git-annex_keys.mdwn +++ b/doc/todo/sha1_collision_embedding_in_git-annex_keys.mdwn @@ -3,6 +3,8 @@ that it could be used for a SHA1 collision attack. So, a signed git commit could point to a tree with such a key in it, and the blob for the key could have two versions with the same SHA1. +> All issues below are [[done]] --[[Joey]] + Users who want to use git-annex with signed commits to mitigate git's own SHA1 insecurities would like at least a way to disable the insecure git-annex backends: @@ -82,7 +84,8 @@ Or, we can document this gotcha. > > change their behavior, although new ones will. That's a mixed > > blessing; it makes it harder to switch an existing repo to disallowing > > SHA1/URL/WORM, but an accidental/malicious re-enabling won't affect -> > clones made while it was disabled. +> > clones made while it was disabled. +> > > This is done now. > > > > Could a repository be configured to either always disallow > > SHA1/URL/WORM, or always allow them, and then not let that be changed? |