From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by mail.saout.de (Postfix) with ESMTP for ; Wed, 14 Jul 2010 08:38:53 +0200 (CEST) Date: Wed, 14 Jul 2010 08:38:56 +0200 From: Heinz Diehl Message-ID: <20100714063856.GA6443@fancy-poultry.org> References: <1279054281.867.5.camel@Koma-Station.localdomain> <4C3CD6C8.6020303@redhat.com> <1279059451.867.23.camel@Koma-Station.localdomain> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: Content-Transfer-Encoding: quoted-printable Subject: Re: [dm-crypt] Wrong behavior? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de On 14.07.2010, MkFly wrote:=20 > Well now I'm wondering, does luksFormat use /dev/urandom for > master-key generation? Yes, it does. > =A0If so, is there any way to force it to use > /dev/random instead (aside from generating a keyfile beforehand and > luksFormat'ing with --master-key-file)? If I remember correctly, this has been discussed here before, and one of the main reasons against using /dev/random was that it's blocking when it's out of entropy.