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

move thoughts

Browse source
This commit is contained in:
Joey Hess 2017-02-25 15:00:22 -04:00
parent a463ba6e8a
commit e8bf942dc4
No known key found for this signature in database
GPG key ID: C910D9222512E3C7
1 changed files with 5 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -86,11 +86,15 @@ Or, we can document this gotcha.
> > > >
> > Could a repository be configured to either always disallow > > Could a repository be configured to either always disallow
> > SHA1/URL/WORM, or always allow them, and then not let that be changed? > > SHA1/URL/WORM, or always allow them, and then not let that be changed?
> > Yes -- Look through all the history of the git-annex branch from the > > Maybe -- Look through all the history of the git-annex branch from the
> > earliest commit forward. The first value stored in > > earliest commit forward. The first value stored in
> > git-annex/disableinsecurehashes (eg 0 or 1) is the value to use; > > git-annex/disableinsecurehashes (eg 0 or 1) is the value to use;
> > any later changes are ignored. > > any later changes are ignored.
> > That would be a little slow, but only needs to be done at init time. > > That would be a little slow, but only needs to be done at init time.
> > It might be possible to fool this though. Create a new empty branch,
> > with an old date, make a commit enabling insecure hashes, and
> > merge it into git-annex branch HEAD. It now looks as if insecure hashes
> > were disabled earliest.
---- ----