From b7eff4a34d98bcc5bd1c995f200306775ee0c7be Mon Sep 17 00:00:00 2001 From: xloem Date: Fri, 3 Mar 2017 12:29:52 +0000 Subject: [PATCH] Added a comment: Non-conforming blobs --- ...comment_1_82241dc5666e1b573a24b3e84f3991ae._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/tips/using_signed_git_commits/comment_1_82241dc5666e1b573a24b3e84f3991ae._comment diff --git a/doc/tips/using_signed_git_commits/comment_1_82241dc5666e1b573a24b3e84f3991ae._comment b/doc/tips/using_signed_git_commits/comment_1_82241dc5666e1b573a24b3e84f3991ae._comment new file mode 100644 index 0000000000..b8f9c787f5 --- /dev/null +++ b/doc/tips/using_signed_git_commits/comment_1_82241dc5666e1b573a24b3e84f3991ae._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="xloem" + avatar="http://cdn.libravatar.org/avatar/b8c087f7c5e6a9358748f0727c077f3b" + subject="Non-conforming blobs" + date="2017-03-03T12:29:51Z" + 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. +"""]]