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

Re: Fetching SHA id's instead of named references?

From
Dmitry Potapov <dpotapov@gmail.com>
Date
Apr 6, 2009, 21:50 UTC
Message-ID
<37fcd2780904061450t62cac214x7588e056a6450bab@mail.gmail.com>
In-Reply-To
<alpine.DEB.1.00.0904061447220.6619@intel-tinevez-2-302>
On Mon, Apr 06, 2009 at 02:48:17PM +0200, Johannes Schindelin wrote:
>_
> The issue is not if someone manages to fetch stuff before you repair it.__
> The issue is that that someone should not be able to manage _after_ you_
> repair it.

But how this someone will know the exact SHA-1 needed to fetch this commit without having seen this commit already? Guessing SHA-1 by brute force attack does not sound very promising...

Dmitry
Previous: Johannes SchindelinNext: Matthieu Moy
Message 5 of 15 in “Fetching SHA id's instead of named references?”
  1. Klas LindbergApr 6, 2009
  2. Johannes SchindelinApr 6, 2009
  3. Klas LindbergApr 6, 2009
  4. Johannes SchindelinApr 6, 2009
  5. Dmitry PotapovApr 6, 2009
  6. Matthieu MoyApr 6, 2009
  7. Klas LindbergApr 6, 2009
  8. Finn Arne GangstadApr 6, 2009
  9. Shawn O. PearceApr 6, 2009
  10. Klas LindbergApr 6, 2009
  11. Nicolas PitreApr 6, 2009
  12. Klas LindbergApr 6, 2009
  13. Nicolas PitreApr 7, 2009
  14. Klas LindbergApr 8, 2009
  15. Nicolas PitreApr 8, 2009

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.