From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Pass+keyfile
Date: Mon, 1 Dec 2014 17:39:20 +0100 [thread overview]
Message-ID: <20141201163919.GA1737@tansi.org> (raw)
In-Reply-To: <5e1359f05d092cc49d6b80ba5941fca5@unseen.is>
On Mon, Dec 01, 2014 at 15:54:45 CET, 0x14@unseen.is wrote:
> >This construction is redundant and does not provide any
> >additional security as compared to passphrase alone,
> >assuming that your passphrase is secure.
>
> Additional security, as I see it, will be:
>
> 1. If you have knowledge about encrypted device, you need to not
> only know the passphrase, but also have the keyfile (have physical
> access to it). Some sort of 2-FA
And now do a scenario where an attacke has the passphrase, but
not root access and not the keyfile. There are not many
possibilities for that to happen and most are unrealistic.
The typical way somebody gets your passphrase is by hacking
your box. Then they also get the master key, the keyfile
and anything else they want. Disk encryption does not protect
against getting hacked.
> 2. Separate keyfile may be easier to physical destruction, it may be
> crucial when you are in hurry to do that - small microsd card with
> keyfile VS encrypted harddrive. If I get it right, bigger encrypted
> containers in plain mode are harder to destroy also.
No. The SD card is a lot _harder_ to destroy than the LUKS header.
The LUKS header is gone after a single overwrite of 2MiB of data.
The SD card needs very careful physical destruction.
Arno
> Isn`t it somehow comparable to having LUKS header on separate device
> (--header option)?
>
> Am I wrong?
>
> Thanks for patience in advance :)
>
> P.S. Writing form another mail, sorry for possible confusion.
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2014-12-01 16:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 14:54 [dm-crypt] Pass+keyfile 0x14
2014-12-01 16:39 ` Arno Wagner [this message]
2014-12-01 16:49 ` Sven Eschenberg
2014-12-01 17:37 ` 0x14
2014-12-01 22:25 ` Arno Wagner
2014-12-02 0:15 ` 0x14
2014-12-02 1:03 ` Arno Wagner
2014-12-02 2:43 ` 0x14
2014-12-02 3:31 ` Arno Wagner
2014-12-02 3:51 ` 0x14
2014-12-02 19:16 ` 0x14
2014-12-02 21:02 ` Arno Wagner
2014-12-02 22:48 ` 0x14
2014-12-02 23:22 ` Arno Wagner
2014-12-02 23:40 ` 0x14
2014-12-03 16:15 ` Arno Wagner
2014-12-03 16:19 ` Dragan Milivojević
-- strict thread matches above, loose matches on Subject: below --
2014-12-01 2:54 0x14
2014-12-01 12:49 ` Arno Wagner
2014-12-01 13:49 ` Quentin Lefebvre
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=20141201163919.GA1737@tansi.org \
--to=arno@wagner.name \
--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.