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

Re: Some issues when trying to set up a shallow git mirror server

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 7, 2016, 18:00 UTC
Message-ID
<xmqq4mep5kyg.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20160107165417.GB3397@logi.codethink.co.uk>
Richard Maw <richard.maw@codethink.co.uk> writes:
Show 10 quoted lines
> This is inconvenient for us,
> as we were explicitly using refspecs which didn't force the fetch,
> since we were using the "non fast-forward update" errors
> to detect whether upstream force pushed important refs
> which could be a sign of tampering.
>
> While the client doesn't have enough information
> the server has those commits.
> Would it make sense for the server to be able to tell the client
> "trust me, that commit is a descendant of the previous one"?

It does not in our security model, as you do not blindly trust the other side, whether you are a "client" or a "server".

Previous: Richard MawNext: Richard Maw
Message 2 of 11 in “Some issues when trying to set up a shallow git mirror server”
  1. Richard MawJan 7, 2016
  2. Junio C HamanoJan 7, 2016
  3. Richard MawJan 8, 2016
  4. Duy NguyenJan 8, 2016
  5. Richard MawJan 8, 2016
  6. Junio C HamanoJan 8, 2016
  7. Richard MawJan 11, 2016
  8. Junio C HamanoJan 12, 2016
  9. Richard MawJan 13, 2016
  10. Junio C HamanoJan 13, 2016
  11. Richard MawJan 13, 2016

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.