From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Detecting the use of a keyfile
Date: Thu, 23 May 2013 16:55:12 +0200 [thread overview]
Message-ID: <20130523145512.GA12471@tansi.org> (raw)
In-Reply-To: <1369315645.16168.140661234738893.257DC401@webmail.messagingengine.com>
On Thu, May 23, 2013 at 03:27:25PM +0200, sector9@ftml.net wrote:
> During the boot stage is it possible for an attacker with physical
> access to detect if a keyfile is used to unlock an encrypted volume?
Yes, very easily. Just look at the initrd or init-script that does it.
Booting with a USB/CD Linux (e.g. Knoppix) makes this easy, including
the test whether the keyfile is valid.
> Does it yield to protest that the keyfile is lost/unknown/destroyed when
> in reality there is no keyfile but instead a regular non-keyfile
> passphrase?
Aehm, what are you asking? Whether you could lie about the former
presence of a keyfile and claim the data is now inacessible due
to its absence? That depends very much so how much technological
knowledge those have that should believe it and what mechnism for
its loss or destruction you propose. Also, keyfiles are not
secure, so you would have to justify the low securuity level and
the absebce of backups as well.
Generally, I would call it a losing strategy.
Arno
--
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
----
There are two ways of constructing a software design: One way is to make it
so simple that there are obviously no deficiencies, and the other way is to
make it so complicated that there are no obvious deficiencies. The first
method is far more difficult. --Tony Hoare
next prev parent reply other threads:[~2013-05-23 14:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 13:27 [dm-crypt] Detecting the use of a keyfile sector9
2013-05-23 14:55 ` Arno Wagner [this message]
2013-05-23 15:21 ` sector9
2013-05-23 15:40 ` Arno Wagner
2013-05-23 17:13 ` sector9
2013-05-23 17:36 ` 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=20130523145512.GA12471@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.