From: Matti Nykyri <matti.nykyri@iki.fi>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] [SOLVED] Running cryptsetup under mdev
Date: Mon, 12 May 2014 10:24:42 +0300 [thread overview]
Message-ID: <4F9346AC-0359-4C36-B24A-90DEB74D1A77@iki.fi> (raw)
In-Reply-To: <adc2d4fb-ef5a-4c35-a3bf-15064e3586ce@email.android.com>
On May 7, 2014, at 21:57, "J. Roeleveld" <joost@antarean.org> wrote:
> I was wondering. What is the actual reason why cryptsetup has a LUKS and non-LUKS set of options?
And a short answer to the actual question :)
LUKS automates key creation and non-LUKS lets you do it manually.
Sorry for the long posts ;)
--
-Matti
next prev parent reply other threads:[~2014-05-12 7:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 18:31 [gentoo-user] Problems with loop-aes Walter Dnes
2014-05-06 18:45 ` J. Roeleveld
2014-05-06 21:34 ` Walter Dnes
2014-05-07 6:11 ` J. Roeleveld
2014-05-07 18:11 ` [gentoo-user] [SOLVED] Running cryptsetup under mdev Walter Dnes
2014-05-07 18:57 ` J. Roeleveld
2014-05-08 10:36 ` Andrew Savchenko
2014-05-12 6:51 ` J. Roeleveld
2014-05-12 7:21 ` Matti Nykyri
2014-05-12 7:24 ` Matti Nykyri [this message]
2014-05-06 21:50 ` [gentoo-user] Problems with loop-aes Alon Bar-Lev
2014-05-07 4:36 ` Walter Dnes
2014-05-07 6:48 ` Alon Bar-Lev
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=4F9346AC-0359-4C36-B24A-90DEB74D1A77@iki.fi \
--to=matti.nykyri@iki.fi \
--cc=gentoo-user@lists.gentoo.org \
/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