From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS disk encryption with remote boot authentication
Date: Mon, 20 Oct 2014 00:10:45 +0200 [thread overview]
Message-ID: <20141019221045.GA3633@tansi.org> (raw)
In-Reply-To: <CAHeB2AmYqVLdcmdjQxuELTAcOsOP3HeFwZEQh4cPNaRG80oJuQ@mail.gmail.com>
On Sun, Oct 19, 2014 at 22:59:21 CEST, Cpp wrote:
> On 10/19/14, Arno Wagner <arno@wagner.name> wrote:
> > Actually, it has a pretty good chance of working well. Once.
> > And if it is not too obvious and nowhere documented that the
> > attacker can get at beforehand.
>
> So basically if a device like this is meant to be used and distributed
> widely, one security requirement would be that each and every device
> uses a custom anti-tampering circuitry setup so that no two setups are
> identical. After one device has been compromised, a new custom setup
> has to be made, possibly at a new location.
For DIY, yes. Commercial HSMs have another protection, namely
they are priced at EUR 50k+. That discourages most attackers from
buying a few to leant how to break into them.
But seriously, this is not a beginner's game. If you want to
keep out a low-resource attacker, just get a safe, drill some
holes for the cables, add an arduino or compatible with light,
vibration and orientation sensors and make it protect the
passphrase and pull the plug if it finds something fishy.
Attachment to computer via serial or USB as HID is fine.
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
----
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-10-19 22:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 11:42 [dm-crypt] LUKS disk encryption with remote boot authentication Cpp
2014-10-14 12:42 ` Ralf Ramsauer
2014-10-14 13:12 ` Arno Wagner
2014-10-14 21:16 ` Jonas Meurer
2014-10-14 21:51 ` Arno Wagner
2014-10-15 6:49 ` Cpp
2014-10-15 11:37 ` Sam Rakowski
2014-10-17 23:47 ` Alex Elsayed
2014-10-17 23:51 ` Alex Elsayed
2014-10-18 3:37 ` Arno Wagner
2014-10-19 19:13 ` Cpp
2014-10-19 19:40 ` Ralf Ramsauer
2014-10-19 20:12 ` Arno Wagner
2014-10-19 20:59 ` Cpp
2014-10-19 22:10 ` Arno Wagner [this message]
2014-10-20 10:09 ` Sven Eschenberg
2014-10-20 13:36 ` Arno Wagner
2014-10-21 4:37 ` Alex Elsayed
2014-10-21 10:01 ` Sven Eschenberg
2014-10-21 13:46 ` Arno Wagner
2014-10-21 14:50 ` Sven Eschenberg
2014-10-21 16:18 ` Arno Wagner
2014-10-21 13:42 ` 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=20141019221045.GA3633@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.