From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS disk encryption with remote boot authentication
Date: Sun, 19 Oct 2014 22:12:30 +0200 [thread overview]
Message-ID: <20141019201230.GA2584@tansi.org> (raw)
In-Reply-To: <544413AC.5040803@ramses-pyramidenbau.de>
On Sun, Oct 19, 2014 at 21:40:28 CEST, Ralf Ramsauer wrote:
> On 10/19/14 22:13, Cpp wrote:
> > This circuitry will
> > be reponsible for physical protection i.e. safe keeping the encryption
> > key and destroy it in case an attacker tries to access it.
> > Use some epoxy to prevent easy access to RAM
> > chips... cold boot anyone?
> Erm, just my two cents, but do you *really* think that this is a threat
> to you?
> In my opinion, costs and benefits should maintain balance...
>
> And I am quite sure that your self-made tamper safe solution will
> probably fail, if someone is really willing to break into your system.
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.
Arno
> So I think ssh'ing to your system and entering the passphrase manually
> remains the best solution.
>
> Cheers
> Ralf
> _______________________________________________
> 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-10-19 20:12 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 [this message]
2014-10-19 20:59 ` Cpp
2014-10-19 22:10 ` Arno Wagner
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=20141019201230.GA2584@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.