483887591dNot quite there yet. Also, changed the format of GITBUNDLE keys to use only one '-' after the UUID. A sha256 does not contain that character, so can just split at the last one. Amusingly, the sha256 will probably not actually be verified. A git bundle contains its own checksums that git uses to verify it. And if someone wanted to replace the content of a GITBUNDLE object, they could just edit the manifest to use a new one whose sha256 does verify. Sponsored-by: Nicholas Golder-Manning |
||
|---|---|---|
| .. | ||
| hashing | ||
| key_format | ||
| lockdown | ||
| comment_1_4b8ed353dca4f484b3b6eb463fa02fd8._comment | ||
| comment_2_c19232d5cc4976c2e5b014aef6e8d9ec._comment | ||
| comment_3_5a26ee5aab274f321a4ea6f8527f53bd._comment | ||
| comment_4_81293b180fb09105ec158fdfef73d249._comment | ||
| comment_5_354012b6a9ac11160eb926234d38051f._comment | ||
| comment_7_7e40f744f9ac7f0403df9d1a2162a516._comment | ||
| comment_7_9c82a2878f3feb1b2a95662ed25b234b._comment | ||
| comment_8_9dccdd3a9556ceef54e318cd5c8a50ad._comment | ||
| comment_9_40442b012886ad698f448c262f0d7f4c._comment | ||
| comment_10_c4298babd96b2596bd4f6ad828212c92._comment | ||
| comment_11_9758bb3a17f63b4dcf51742ea482dbe9._comment | ||
| comment_12_f0325cefa5cd53a5a897046606137cef._comment | ||
| comment_13_e45b6fa035a30703618448a0f764f935._comment | ||
| comment_14_3f62751c2dd041f4ead1c6580ea5eec1._comment | ||
| comment_15_c3d12d14e4d044f39829c5d92f523655._comment | ||
| comment_16_2455c898d6c77a5437a2c1532144bb8a._comment | ||
| comment_17_df13b7e66963a6d2673e49f52afb978a._comment | ||
| comment_18_1adce7945940b9c384c2383261388dd9._comment | ||
| git-remote-annex.mdwn | ||
| hashing.mdwn | ||
| key_format.mdwn | ||
| lockdown.mdwn | ||
| pointer_file.mdwn | ||