Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <002501bfc549$7d19f1c0$c85a9b86@vwl.unimannheim.de>
From: "Daniel Probst" <daniel DOT probst AT vwl DOT uni-mannheim DOT de>
To: <cygwin AT sourceware DOT cygnus DOT com>
Subject: /dev/random
Date: Wed, 24 May 2000 08:30:00 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600

The cygwin implementation seems to be based on the MS Crypto API. Is this
right?
Well this is certainly better than no /dev/random, but I do feel uneasy
about using it for crypto purposes.
Why didn't one choose another entropy generator? Was it purely time/priority
considerations? How about the Bruce Shneier (Counterplane) open-source
YARROW module.
-dan



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com