DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Entropy available for luksFormat during GNU/Linux	installs
Date: Mon, 25 Jan 2010 00:03:54 +0100	[thread overview]
Message-ID: <20100124230354.GA24786@tansi.org> (raw)
In-Reply-To: <20100124140205.GA22492@fancy-poultry.org>

On Sun, Jan 24, 2010 at 03:02:05PM +0100, Heinz Diehl wrote:
> On 24.01.2010, Arno Wagner wrote: 
> 
> > "As  a  general rule,  /dev/urandom  should  be  used  for everything 
> >  except long-lived GPG/SSL/SSH keys."
> >  ^^^^^^ 
> 
> Why?
> 
> Is the output of urandom somehow more predictable than random?

In a low environmental Entropy situation for a newly installed
system, it is. For example it will give you a 512 bit key, even
if it has only gathered 32 bits of entropy. The attacker then
needs to try all 512 bit keys generated with the possible
different 32 bit initializations to find the key. It is not
an attack that really matters when there is a user at the
keyboard, and a mouse in use. Think of fully automated
installation with no user interaction on a very simple
system not connected to the network.

/dev/random will, in contrast, make you wait until it
has gathered signbificantly more entropy than the 512 bits
before giving you the key.

Arno

-- 
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name 
GnuPG:  ID: 1E25338F  FP: 0C30 5782 9D93 F785 E79C  0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier 

  parent reply	other threads:[~2010-01-24 23:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-24  6:17 [dm-crypt] Entropy available for luksFormat during GNU/Linux installs Roscoe
2010-01-24 10:50 ` Milan Broz
2010-01-24 13:11   ` Arno Wagner
2010-01-24 14:02     ` Heinz Diehl
2010-01-24 14:31       ` Rick Moritz
2010-01-24 16:56         ` Heinz Diehl
2010-01-24 23:11           ` Arno Wagner
2010-01-24 23:03       ` Arno Wagner [this message]
2010-01-25 11:25         ` Milan Broz
2010-02-03  0:45           ` Roscoe
2010-02-03  6:21             ` Arno Wagner
2010-02-03  7:57               ` Arno Wagner
2010-02-03 12:31                 ` Roscoe
2010-02-03  8:56             ` Milan Broz
     [not found]               ` <cf657bae1002030430l3b0f4768x19e917466b5664bb@mail.gmail.com>
     [not found]                 ` <4B697D55.5020304@redhat.com>
     [not found]                   ` <cf657bae1002031231s6dd17c8bq118e5c5276c31b84@mail.gmail.com>
2010-03-23  8:43                     ` Roscoe
  -- strict thread matches above, loose matches on Subject: below --
2010-01-24 18:12 Si St

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=20100124230354.GA24786@tansi.org \
    --to=arno@wagner.name \
    --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