From: Jakub Narebski <jnareb@gmail.com>
To: Chris Frey <cdfrey@foursquare.net>
Cc: git@vger.kernel.org
Subject: Re: Supporting hashes other than SHA-1
Date: Tue, 12 May 2009 05:55:43 -0700 (PDT) [thread overview]
Message-ID: <m3vdo6lbuy.fsf@localhost.localdomain> (raw)
In-Reply-To: <m3zldjl5bq.fsf@localhost.localdomain>
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/
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-05-12 13:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 19:52 Supporting hashes other than SHA-1 Chris Frey
2009-05-11 21:04 ` Jakub Narebski
2009-05-12 12:55 ` Jakub Narebski [this message]
2009-05-12 13:59 ` Andreas Ericsson
2009-05-12 14:06 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3vdo6lbuy.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=cdfrey@foursquare.net \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.