From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by mail.saout.de (Postfix) with ESMTP for ; Thu, 27 May 2010 20:21:15 +0200 (CEST) Message-ID: <4BFEB817.5070007@redhat.com> Date: Thu, 27 May 2010 20:21:11 +0200 From: Milan Broz MIME-Version: 1.0 References: <20100527145130.17205j9xtswbuacc@webmail.physik.uni-muenchen.de> <4BFE796E.9020806@redhat.com> <1274970037.20140.40.camel@etppc09.garching.physik.uni-muenchen.de> <4BFE857B.6010906@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [dm-crypt] miscellaneous dm-crypt/LUKS/cryptsetup questions List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Mario 'BitKoenig' Holbe Cc: dm-crypt@saout.de On 05/27/2010 06:21 PM, Mario 'BitKoenig' Holbe wrote: > Milan Broz wrote: >> (read from /dev/random can return if there is not enough entropy, it needs > > Nope. It blocks. yep, you are right :) The problem is that can wait very long time, so it should inform user that system is out of entropy and ask for some action etc. This should be part of the RNG handler in cryptsetup if using /dev/random is supported. Milan