All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] passfrase or dev_random for keyfile of a	dmcrypt_swap
Date: Mon, 19 Apr 2010 18:54:58 +0200	[thread overview]
Message-ID: <20100419165458.GA27932@tansi.org> (raw)
In-Reply-To: <20100419163745.C906144B6C@ws5-1.us4.outblaze.com>

On Mon, Apr 19, 2010 at 05:37:45PM +0100, Si St wrote:
> What should be recommended:

> 
> To apply either /dev/random or a passfrase for the establishment of a
> keyfile to a swap partition?

Allways /dev/random, unless you have a low-entropy scenario,
in which you may have to combine it with a stored and updated
seed.

> I am thinking about a potential crash and the consequences if the swap
> partition has to be used for rebuild of something. Then a /dev/random or
> if necessary /dev/urandom would not be so good.

The swap partition is not used in reconstructing things under
Linux.
 
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 

  reply	other threads:[~2010-04-19 16:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-19 16:37 [dm-crypt] passfrase or dev_random for keyfile of a dmcrypt_swap Si St
2010-04-19 16:54 ` Arno Wagner [this message]
2010-04-19 19:01 ` Heinz Diehl
2010-04-20  5:41 ` Luca Berra
  -- strict thread matches above, loose matches on Subject: below --
2010-04-20 14:15 Si St
2010-04-20 15:15 ` Arno Wagner
2010-04-21  8:34 ` Heinz Diehl
2010-04-21  9:06   ` Jonas Meurer
2010-04-20 18:06 Si St
2010-04-20 19:14 ` Arno Wagner

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=20100419165458.GA27932@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.