Re: SHA1 collisions found

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

Subject: Re: SHA1 collisions found
From: Ian Jackson <ijackson@xxxxxxxxxxxxxxxxxxxxxx>
Date: Sat, 25 Feb 2017 00:06:45 +0000
In-reply-to: <22704.50445.435156.883001@chiark.greenend.org.uk>
References: <20170223164306.spg2avxzukkggrpb@kitenet.net> <22704.19873.860148.22472@chiark.greenend.org.uk> <xmqq60jz5wbm.fsf@gitster.mtv.corp.google.com> <22704.50445.435156.883001@chiark.greenend.org.uk>

Ian Jackson writes ("Re: SHA1 collisions found"):
> The idea of using the length is a neat trick, but it cannot support
> the dcurrent object name abbreviation approach unworkable.

Sorry, it's late here and my grammar seems to have disintegrated !

Ian.

References:
- SHA1 collisions found
  - From: Joey Hess
- Re: SHA1 collisions found
  - From: Ian Jackson
- Re: SHA1 collisions found
  - From: Junio C Hamano
- Re: SHA1 collisions found
  - From: Ian Jackson

Prev by Date: [PATCH 4/5] ls-files: illustrate bug when recursing with relative pathspec
Next by Date: Re: SHA1 collisions found
Previous by thread: Re: SHA1 collisions found
Next by thread: Re: SHA1 collisions found
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]