From: "Jorge Fábregas" <jorge.fabregas@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Passphrase protected key file?
Date: Tue, 12 Jul 2011 07:40:28 -0400 [thread overview]
Message-ID: <4E1C32AC.5040806@gmail.com> (raw)
In-Reply-To: <20110711231732.596b8622.ldarby@tuffmail.com>
On 07/11/2011 06:17 PM, Laurence Darby wrote:
> gpg -d ~/pass_key | cryptsetup luksOpen --key-file - /dev/loop1 loop1
I don't see the point of this. If you need to enter a passphrase for
GPG to decrypt your stored key...why not simply use a passphrase
(instead of a key file) for cryptsetup? In both cases you would be
entering a passphrase (so the manual work is the same). Also, if you
use just a passphrase for cryptsetup I see an advantage there: there's
no hash or "encrypted version" of my passphrase stored _anywhere_ on the
system.
Regards,
Jorge
next prev parent reply other threads:[~2011-07-12 11:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 22:17 [dm-crypt] Passphrase protected key file? Laurence Darby
2011-07-12 11:40 ` Jorge Fábregas [this message]
2011-07-12 12:47 ` Arno Wagner
2011-07-14 9:10 ` Ma Begaj
2011-07-14 11:04 ` Arno Wagner
2011-07-14 11:55 ` Ma Begaj
2011-07-14 13:35 ` Arno Wagner
2011-07-14 14:12 ` Heiko Rosemann
2011-07-14 14:46 ` [dm-crypt] Status of trim for SSds? André Gall
2011-07-14 15:55 ` Milan Broz
2011-07-14 16:04 ` Christoph Anton Mitterer
2011-07-14 16:39 ` Philipp Wendler
2011-07-14 16:52 ` Milan Broz
2011-07-14 17:14 ` Philipp Wendler
2011-07-15 13:59 ` Christian Hesse
2011-07-15 14:48 ` Milan Broz
2011-07-18 8:45 ` Christian Hesse
2011-07-18 10:04 ` Milan Broz
2011-07-18 10:16 ` Christian Hesse
2011-07-21 12:55 ` Christian Hesse
2011-07-24 17:18 ` MkFly
2011-07-24 18:34 ` Milan Broz
2011-07-14 19:27 ` [dm-crypt] Passphrase protected key file? Arno Wagner
2011-07-14 21:21 ` Heiko Rosemann
2011-07-14 21:44 ` Arno Wagner
2011-07-15 5:33 ` Iggy
2011-08-03 12:09 ` Laurence Darby
2011-08-03 13:41 ` Arno Wagner
2011-08-03 11:35 ` Laurence Darby
2011-08-03 13:45 ` 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=4E1C32AC.5040806@gmail.com \
--to=jorge.fabregas@gmail.com \
--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.