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

Re: [PATCH] diff.c: Ensure "index $from..$to" line contains unambiguous SHA1s

From
Johannes Sixt <j6t@kdbg.org>
Date
May 30, 2010, 19:58 UTC
Message-ID
<201005302158.40314.j6t@kdbg.org>
In-Reply-To
<201005301537.18039.johan@herland.net>
On Sonntag, 30. Mai 2010, Johan Herland wrote:
Show 10 quoted lines
> +cat >expect_initial <<EOF
> +100644 blob 51d2738463ea4ca66f8691c91e33ce64b7d41bb1	foo
> +EOF
> +
> +cat >expect_update <<EOF
> +100644 blob 51d2738efb4ad8a1e40bed839ab8e116f0a15e47	foo
> +EOF
> +
> +test_expect_success 'setup' '
> +	echo 4827 > foo &&
...
> +	echo 11742 > foo &&

How the fscking hell did you find these two simple values that are an almost-SHA1-collision? It's easier to hit the jackpot!?!

-- Hannes
Previous: Johan HerlandNext: Johan Herland
Message 2 of 3 in “diff.c: Ensure "index $from..$to" line contains unambiguous SHA1s”
  1. diff.c: Ensure "index $from..$to" line contains unambiguous SHA1sJohan Herland, May 30, 2010
  2. Johannes SixtMay 30, 2010
  3. Johan HerlandMay 30, 2010

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.