All of lore.kernel.org
 help / color / mirror / Atom feed
From: lyz <lyz@riseup.net>
To: dm-crypt@saout.de
Subject: [dm-crypt] Security concern: gpg keyfile vs passphrase
Date: Tue, 07 Jul 2015 22:32:49 +0200	[thread overview]
Message-ID: <559C3771.2030705@riseup.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 458 bytes --]

Hi all,

I'm encrypting my whole system under LUKS, and I've seen that in the
wiki of Arch and Gentoo they suggest to use a keyfile and encrypt it
with gpg.

Why is more secure to encrypt a keyfile with a passphrase and then
encrypt the device with the keyfile rather than encrypting the device
directly with the passphrase?

Against a brute force attack the passphrase is the same, so they should
be equally secure, am I wrong?

Thank you



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2015-07-07 20:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07 20:32 lyz [this message]
2015-07-07 21:00 ` [dm-crypt] Security concern: gpg keyfile vs passphrase wintonian
     [not found] ` <559C3C05.9040701@wintonian.org.uk>
2015-07-07 21:08   ` lyz
2015-07-07 21:20     ` Arno Wagner
2015-07-09 19:00       ` Sven Eschenberg
2015-07-08  3:00 ` David Christensen

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=559C3771.2030705@riseup.net \
    --to=lyz@riseup.net \
    --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.