diff options
| author |  xloem <xloem@web> | 2017-03-03 12:32:35 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2017-03-03 12:32:35 +0000 |
| commit | 16da107ff592c933b3c12236664eaf83b3b8435d (patch) | |
| tree | a568a93d7d0eb549de867866cbf42efc73e7057b | |
| parent | 14b37273f911410da8c562ed1cf695208ee08f0f (diff) | |
removed
| -rw-r--r-- | doc/tips/using_signed_git_commits/comment_2_0dc5119944132808299da2092b01b25f._comment | 10 |
1 files changed, 0 insertions, 10 deletions
diff --git a/doc/tips/using_signed_git_commits/comment_2_0dc5119944132808299da2092b01b25f._comment b/doc/tips/using_signed_git_commits/comment_2_0dc5119944132808299da2092b01b25f._comment deleted file mode 100644 index 3678bbae3..000000000 --- a/doc/tips/using_signed_git_commits/comment_2_0dc5119944132808299da2092b01b25f._comment +++ /dev/null @@ -1,10 +0,0 @@ -[[!comment format=mdwn - username="xloem" - avatar="http://cdn.libravatar.org/avatar/b8c087f7c5e6a9358748f0727c077f3b" - subject="Non-conforming blobs" - date="2017-03-03T12:30:34Z" - content=""" -It seems git-annex needs some way to verify that all blobs match its expected format for this security to be strong. My histories have tons of huge binary blobs in them from when I tried upgrading to v6 before it was stable and got a lot of data committed raw. I guess I need to rewrite my history to contain only verified blobs? - -It's really too bad git hasn't upgraded to a newer hashing function by now. They should make a plan to do that at least once a decade. -"""]] |