From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mbroz@redhat.com>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
	by mail.saout.de (Postfix) with ESMTP
	for <dm-crypt@saout.de>; Wed, 14 Jul 2010 10:20:33 +0200 (CEST)
Received: from int-mx08.intmail.prod.int.phx2.redhat.com
	(int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.21])
	by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id o6E8KWCc005423
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK)
	for <dm-crypt@saout.de>; Wed, 14 Jul 2010 04:20:32 -0400
Received: from [10.36.8.3] (vpn2-8-3.ams2.redhat.com [10.36.8.3])
	by int-mx08.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP
	id o6E8KVkM021562
	for <dm-crypt@saout.de>; Wed, 14 Jul 2010 04:20:31 -0400
Message-ID: <4C3D734F.6040502@redhat.com>
Date: Wed, 14 Jul 2010 10:20:31 +0200
From: Milan Broz <mbroz@redhat.com>
MIME-Version: 1.0
References: <1279054281.867.5.camel@Koma-Station.localdomain>	<4C3CD6C8.6020303@redhat.com>	<1279059451.867.23.camel@Koma-Station.localdomain>	<AANLkTilvdewwcdzdm2uX6go9q2dahLX7Fes-lwDNOkvU@mail.gmail.com>	<AANLkTimT_9DCXRup6JhGYnBdQqxa51n09e-trTMUXRKj@mail.gmail.com>
	<20100714063856.GA6443@fancy-poultry.org>
In-Reply-To: <20100714063856.GA6443@fancy-poultry.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [dm-crypt] Wrong behavior?
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
	<mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
	<mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

On 07/14/2010 08:38 AM, Heinz Diehl wrote:
> On 14.07.2010, MkFly wrote: 
> 
>> Well now I'm wondering, does luksFormat use /dev/urandom for
>> master-key generation?
> 
> Yes, it does.

I want add rng selection to 1.3.x, no eta yet, there is issue for that
on project page. And several discussions already:-)

I was quite disapponted how gcrypt RNG works so code will stick
with using /dev/random for long-term key, urandom for other things (wipe, salt).

There will be option to use RNG for key generation - for now it should
support random/urandom/gcrypt(very strong) RNG (with /dev/random as default).

Milan