diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2017-02-27 13:50:00 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2017-02-27 13:55:15 -0400 |
| commit | cde3a924aec6bcd47ede650572bffa8c414243cf (patch) | |
| tree | daf3c2b27c92372035e712a34668dd17133539e2 /CHANGELOG | |
| parent | 48119806dd24214e88f3f3c62f4dcb14b60dc207 (diff) | |
make fsck check annex.securehashesonly, and new tip for working around SHA1 collisions with git-annex
This commit was sponsored by andrea rota.
Diffstat (limited to 'CHANGELOG')
| -rw-r--r-- | CHANGELOG | 8 |
1 files changed, 5 insertions, 3 deletions
@@ -2,9 +2,11 @@ git-annex (6.20170215) UNRELEASED; urgency=medium * Cryptographically secure hashes can be forced to be used in a repository, by setting annex.securehashesonly. - This does not prevent the git repository from containing files - with insecure hashes, but it does prevent the content of such files - from being added to .git/annex/objects. + This does not prevent the git repository from containing links + to insecure hashes, but it does prevent the content of such files + from being added to .git/annex/objects by any method. + * fsck: Warn about any files whose content is present, that don't + use secure hashes, when annex.securehashesonly is set. * sync, merge: Fail when the current branch has no commits yet, instead of not merging in anything from remotes and appearing to succeed. * Run ssh with -n whenever input is not being piped into it, |