From: Heinz Diehl <htd@fancy-poultry.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Wrong behavior?
Date: Wed, 14 Jul 2010 08:38:56 +0200 [thread overview]
Message-ID: <20100714063856.GA6443@fancy-poultry.org> (raw)
In-Reply-To: <AANLkTimT_9DCXRup6JhGYnBdQqxa51n09e-trTMUXRKj@mail.gmail.com>
On 14.07.2010, MkFly wrote:
> Well now I'm wondering, does luksFormat use /dev/urandom for
> master-key generation?
Yes, it does.
> If 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.
next prev parent reply other threads:[~2010-07-14 6:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-13 20:51 [dm-crypt] Wrong behavior? Sven Eschenberg
2010-07-13 21:12 ` Milan Broz
2010-07-13 22:17 ` Sven Eschenberg
[not found] ` <AANLkTilvdewwcdzdm2uX6go9q2dahLX7Fes-lwDNOkvU@mail.gmail.com>
2010-07-14 6:07 ` MkFly
2010-07-14 6:38 ` Heinz Diehl [this message]
2010-07-14 8:20 ` Milan Broz
2010-07-14 10:09 ` Arno Wagner
2010-07-14 18:09 ` Christoph Anton Mitterer
2010-07-14 7:58 ` Milan Broz
2010-07-14 11:39 ` Sven Eschenberg
2010-07-14 11:52 ` Milan Broz
2010-07-14 12:07 ` Sven Eschenberg
2010-07-14 12:13 ` Arno Wagner
2010-07-14 12:53 ` Milan Broz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100714063856.GA6443@fancy-poultry.org \
--to=htd@fancy-poultry.org \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox