From: Florian Weimer <fw@deneb.enyo.de>
To: git@vger.kernel.org
Subject: Re: Starting to think about sha-256?
Date: Tue, 29 Aug 2006 08:17:02 +0200 [thread overview]
Message-ID: <87fyfg83s1.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <44F1DCB7.6020804@garzik.org> (Jeff Garzik's message of "Sun, 27 Aug 2006 13:56:07 -0400")
* Jeff Garzik:
> * likely more CPU cycles per hash, though I haven't measured.
According to a quick test using "openssl speed", it's a factor of two
to four, depending on the input size (the difference is less
pronounced for small input sizes).
> Maybe sha-256 could be considered for the next major-rev of git?
And in 2008, you'd have to rewrite history again, to use the next
"stronger" hash function? Do you think that's really necessary or
desirable? Most users will have good control over what data enters
their repositories, so they can spot the evil twins thanks to their
high-entropy contents. Obviously, a second preimage attack would
mattr, but even for MD5, we aren't close to that one AFAIK.
next prev parent reply other threads:[~2006-08-29 12:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-27 17:56 Starting to think about sha-256? Jeff Garzik
2006-08-27 20:30 ` Krzysztof Halasa
[not found] ` <Pine.LNX.4.64.0608271343120.27779@g5.o sdl.org>
2006-08-27 20:46 ` Linus Torvalds
2006-08-27 21:14 ` Krzysztof Halasa
2006-08-27 22:02 ` Johannes Schindelin
2006-08-27 22:35 ` Linus Torvalds
2006-08-28 17:27 ` David Lang
2006-08-28 17:56 ` Linus Torvalds
2006-08-28 18:06 ` Linus Torvalds
2006-08-28 18:32 ` Jeff King
2006-08-28 18:46 ` Linus Torvalds
2006-08-28 19:00 ` Jeff King
2006-08-28 20:12 ` Krzysztof Halasa
2006-08-28 20:20 ` Linus Torvalds
2006-08-28 21:12 ` Krzysztof Halasa
2006-08-28 21:23 ` Linus Torvalds
2006-08-28 23:09 ` Johannes Schindelin
2006-08-28 23:48 ` Linus Torvalds
2006-08-29 6:17 ` Florian Weimer [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-05 9:05 linux
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=87fyfg83s1.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).