From: Jonas Meurer <jonas@freesources.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] encrypted SWAP FAQ item
Date: Thu, 11 Jul 2013 11:24:22 +0200 [thread overview]
Message-ID: <51DE79C6.7010306@freesources.org> (raw)
In-Reply-To: <20130711065320.GA19568@tansi.org>
Heya,
Am 11.07.2013 08:53, schrieb Arno Wagner:
> Dear all,
>
> I just have added a mini-HOWOT on how to set up encrypted swap
> in FAQ item 2.2:
> http://code.google.com/p/cryptsetup/wiki/FrequentlyAskedQuestions
>
> Proofreading and suggestions welcome.
Good idea to add it to the FAQ. Thanks for maintaining this very
valuable piece of documentation.
But maybe you should more emphasize the fact that /etc/crypttab
implementations are distro-specific. While I know for sure that options
like swap and noearly are supported in Debian-based distributions, I'm
not sure about Redhat-based ones. Last time I looked, only a small
subset of crypttab options that we've implemented in Debian were
supported on Redhat-based systems.
Additionally, the following sentence looks wrong to me:
"Note: use /dev/random if you are paranoid or in a potential low-entropy
situation (embedded system, etc.).".
Mainly in low-entropy situations /dev/random would cause the boot
process to hang, right? So for these setups /dev/urandom actually is the
better solution. Granted that one isn't paranoid ;)
Kind regards,
jonas
next prev parent reply other threads:[~2013-07-11 9:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 6:53 [dm-crypt] encrypted SWAP FAQ item Arno Wagner
2013-07-11 7:14 ` .. ink ..
2013-07-11 7:47 ` Arno Wagner
2013-07-11 7:59 ` Justin Tracey
2013-07-11 8:03 ` Arno Wagner
2013-07-11 9:24 ` Jonas Meurer [this message]
2013-07-11 11:58 ` Milan Broz
2013-07-11 15:44 ` Arno Wagner
2013-07-11 10:19 ` octane indice
2013-07-13 2:32 ` Robert Nichols
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=51DE79C6.7010306@freesources.org \
--to=jonas@freesources.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