summaryrefslogtreecommitdiff
path: root/doc/tips/using_signed_git_commits/comment_2_0dc5119944132808299da2092b01b25f._comment
diff options
context:
space:
mode:
authorGravatar xloem <xloem@web>2017-03-03 12:30:35 +0000
committerGravatar admin <admin@branchable.com>2017-03-03 12:30:35 +0000
commit14b37273f911410da8c562ed1cf695208ee08f0f (patch)
tree474cd41c3d7856e58d04bc6957209d26eb972c38 /doc/tips/using_signed_git_commits/comment_2_0dc5119944132808299da2092b01b25f._comment
parent8a396d333358c3d7d87870d5dcf390daa675efa7 (diff)
Added a comment: Non-conforming blobs
Diffstat (limited to 'doc/tips/using_signed_git_commits/comment_2_0dc5119944132808299da2092b01b25f._comment')
-rw-r--r--doc/tips/using_signed_git_commits/comment_2_0dc5119944132808299da2092b01b25f._comment10
1 files changed, 10 insertions, 0 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
new file mode 100644
index 000000000..3678bbae3
--- /dev/null
+++ b/doc/tips/using_signed_git_commits/comment_2_0dc5119944132808299da2092b01b25f._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: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.
+"""]]