From: Laurence Darby <ldarby@tuffmail.com>
To: dm-crypt@saout.de
Subject: [dm-crypt] Passphrase protected key file?
Date: Mon, 11 Jul 2011 23:17:32 +0100 [thread overview]
Message-ID: <20110711231732.596b8622.ldarby@tuffmail.com> (raw)
Hello,
My next question, what's the best way to have a passphrase protected key file?
Should I encrypt it with GPG, and then do eg:
gpg -d ~/pass_key | cryptsetup luksOpen --key-file - /dev/loop1 loop1
That has the advantage of using the same passphrase I use for
everything else, but is there any security risk I'm not seeing? I read
that encrypting something twice or with multiple ciphers is effectively
a new unknown cipher, potentially trivially breakable - I don't think
that applies here, but is there anything like that I need to watch out for?
Alternatively, I could just do this:
( cat ~/pass_key ; cat ) | cryptsetup luksOpen --key-file - /dev/loop1 loop1
so I still have to provide both the key and passphrase, terminated with
Ctrl-D. Any thoughts?
Thanks,
Laurence
next reply other threads:[~2011-07-11 22:17 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 22:17 Laurence Darby [this message]
2011-07-12 11:40 ` [dm-crypt] Passphrase protected key file? Jorge Fábregas
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=20110711231732.596b8622.ldarby@tuffmail.com \
--to=ldarby@tuffmail.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.