git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Verifiable git archives?

From
ALAndy Lutomirski <luto@amacapital.net>
Date
Jan 9, 2014, 03:10 UTC
Message-ID
<CALCETrU88evB6VQrE8=8vrc+HYXAX8_Zx7TsYZp6YXeE4dZdvg@mail.gmail.com>

It's possible, in principle, to shove enough metadata into the output of 'git archive' to allow anyone to verify (without cloning the repo) to verify that the archive is a correct copy of a given commit. Would this be considered a useful feature?

Presumably there would be a 'git untar' command that would report failure if it fails to verify the archive contents.

This could be as simple as including copies of the commit object and all relevant tree objects and checking all of the hashes when untarring.

(Even better: allow subsets of the repository to be archived and verified as well.)

--Andy
Next: Stefan Beller
Message 1 of 9 in “Verifiable git archives?”
  1. Andy LutomirskiJan 9, 2014
  2. Stefan BellerJan 9, 2014
  3. Junio C HamanoJan 9, 2014
  4. Andy LutomirskiJan 9, 2014
  5. Junio C HamanoJan 9, 2014
  6. Andy LutomirskiJan 9, 2014
  7. Michael HaggertyJan 19, 2014
  8. Junio C HamanoJan 21, 2014
  9. Andy LutomirskiJan 25, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.