Re: md5 collision
- From: Michael Heiming <michael+USENET@xxxxxxxxxxxxxx>
- Date: Thu, 1 Dec 2005 22:25:49 +0100
In comp.os.linux.security matt_left_coast <not@xxxxxxxxxx>:
> Unruh wrote:
>> matt_left_coast <not@xxxxxxxxxx> writes:
>>
>>>Unruh wrote:
>>
>>>>>When dealing with the first case, you create the first of the two files,
>>>>>then the file IS known. Then you would be dealing with the second case.
>>>>
>>>> But you have to create them together. You cannot create one and then
>>>> make another which has the same md5.
>>
>>>Exact process, please.
>>
>> Go read the papers.
> Well, I'll take that as proof you are just bull shitting, as I thought.
Please calm down.
This should give a little more insight:
http://www.cits.rub.de/MD5Collisions/
There is heavily math involved, so you can be sure Bill is almost
always right.
--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo zvpunry@xxxxxxxxxx | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 301: appears to be a Slow/Narrow SCSI-0 Interface
problem
.
- Follow-Ups:
- Re: md5 collision
- From: matt_left_coast
- Re: md5 collision
- References:
- md5 collision
- From: julissa . leones
- Re: md5 collision
- From: Unruh
- Re: md5 collision
- From: Ralf Fassel
- Re: md5 collision
- From: Unruh
- Re: md5 collision
- From: matt_left_coast
- Re: md5 collision
- From: Unruh
- Re: md5 collision
- From: matt_left_coast
- Re: md5 collision
- From: Unruh
- Re: md5 collision
- From: matt_left_coast
- md5 collision
- Prev by Date: Re: Wish list
- Next by Date: Re: md5 collision
- Previous by thread: Re: md5 collision
- Next by thread: Re: md5 collision
- Index(es):