[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

SHA1 collisions proven possisble

Subject: SHA1 collisions proven possisble
From: randy at psg.com (Randy Bush)
Date: Mon, 27 Feb 2017 11:18:20 +0700
In-reply-to: <CAJj1h3FK_pV-_wh6G-Rik5qUMBF8xc_=LsBePmK3gO=3Q6Fd5g@mail.gmail.com>
References: <CAPiURgU8UPW9jFzvvf_5D9sX-tyP6qna=wfR4SgLETTbri3uBA@mail.gmail.com> <CAD6AjGT_gvTyifvQOU4z-PNmuCjxOm9DqBvjvomR-9Qvmkg1uw@mail.gmail.com> <[email protected]> <[email protected]> <[email protected]> <CAJj1h3FK_pV-_wh6G-Rik5qUMBF8xc_=LsBePmK3gO=3Q6Fd5g@mail.gmail.com>

> Git prefixes blobs with its own data. You're not going to break git with a
> SHA-1 binary collision.

http://www.metzdowd.com/pipermail/cryptography/2017-February/031623.html

References:
- SHA1 collisions proven possisble
  - From: shortdudey123 at gmail.com (Grant Ridder)
- SHA1 collisions proven possisble
  - From: cb.list6 at gmail.com (Ca By)
- SHA1 collisions proven possisble
  - From: patrick at ianai.net (Patrick W. Gilmore)
- SHA1 collisions proven possisble
  - From: jfbeam at gmail.com (Ricky Beam)
- SHA1 collisions proven possisble
  - From: jhellenthal at dataix.net (J. Hellenthal)
- SHA1 collisions proven possisble
  - From: richard.hesse at weebly.com (Richard Hesse)

Prev by Date: SHA1 collisions proven possisble
Next by Date: SHA1 collisions proven possisble
Previous by thread: SHA1 collisions proven possisble
Next by thread: SHA1 collisions proven possisble
Index(es):
- Date
- Thread