From owner-freebsd-bugs@FreeBSD.ORG  Mon May 12 01:38:13 2003
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8DA5037B401
	for <bugs@freebsd.org>; Mon, 12 May 2003 01:38:13 -0700 (PDT)
Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 868F443FDD
	for <bugs@freebsd.org>; Mon, 12 May 2003 01:38:11 -0700 (PDT)
	(envelope-from netch@segfault.kiev.ua)
Received: (from netch@localhost)
	by segfault.kiev.ua (8) id h5C8c8dD068629;
	Mon, 12 May 2003 11:38:08 +0300 (EEST)
	(envelope-from netch)
Date: Mon, 12 May 2003 11:38:07 +0300
From: Valentin Nechayev <netch@netch.kiev.ua>
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
Message-ID: <20030512083807.GL73391@netch.kiev.ua>
References: <3EBED741.9050000@bcgreen.com>
	<3117.1052695028@critter.freebsd.dk.lucky.freebsd.bugs>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3117.1052695028@critter.freebsd.dk.lucky.freebsd.bugs>
X-42: On
cc: bugs@freebsd.org
Subject: Re: /dev/random and /dev/urandom
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: netch@netch.kiev.ua
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 12 May 2003 08:38:13 -0000

 Sun, May 11, 2003 at 23:29:32, phk wrote about "Re: /dev/random and /dev/urandom": 

> There is one current concern with MD5: over-ratio of collisions.
> 
> What this means is that it may be a bit too easy to find a
> MD5 input which generates a given MD5 output.

Sorry, I might forget cryptography news for a few last years.
Do you say there is _real_ example of two different data streams producing
identical MD5 output _of its full length_?
Please show an URL if things are already on this way...


-netch-