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

Re: Supporting hashes other than SHA-1

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
May 12, 2009, 14:06 UTC
Message-ID
<alpine.DEB.1.00.0905121604560.4447@intel-tinevez-2-302>
In-Reply-To
<4A0980C8.7060106@op5.se>
Hi,
On Tue, 12 May 2009, Andreas Ericsson wrote:
Show 20 quoted lines
> Jakub Narebski wrote:
> > Jakub Narebski <jnareb@gmail.com> writes:
> > 
> > > Chris Frey <cdfrey@foursquare.net> writes:
> > >
> > > > Considering the recent news regarding SHA-1's newly found weaknesses,
> > > > is there any general interest in making git flexible enough to support
> > > > other hashes in the future?
> > > First, there isn't as far as I know any 'known preimage' attack
> > > against SHA-1, and only that would truly matter for Git.
> > >
> > > Second, this issue was discussed in depth in the past; check git
> > > mailing list archives, please...
> > 
> > See also this blog entry (and comments):
> >   http://kitenet.net/~joey/blog/entry/sha-1/
> > 
> 
> It's a bit harder than that, since both pre-images have to be the same
> size.

They don't. The pre-images prefixed by the type identifier and the size in ASCII need to have the same hash. There is a difference.

Ciao, Dscho

Previous: Andreas Ericsson
Message 5 of 5 in “Supporting hashes other than SHA-1”
  1. Chris FreyMay 11, 2009
  2. Jakub NarebskiMay 11, 2009
  3. Jakub NarebskiMay 12, 2009
  4. Andreas EricssonMay 12, 2009
  5. Johannes SchindelinMay 12, 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.