From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Quick dm-crypt questions
Date: Wed, 29 Oct 2014 15:59:01 +0100 [thread overview]
Message-ID: <20141029145900.GC11970@tansi.org> (raw)
In-Reply-To: <5450C274.6020909@ramses-pyramidenbau.de>
On Wed, Oct 29, 2014 at 11:33:24 CET, Ralf Ramsauer wrote:
> On 29.10.2014 11:24, Cpp wrote:
> > The thing is I planned to use a microcontroller to store an encryption
> > key in its RAM, and I see the device uses SRAM, so this might be a
> > problem?
> > http://www.atmel.com/Images/Atmel-8271-8-bit-AVR-Microcontroller-ATmega48A-48PA-88A-88PA-168A-168PA-328-328P_datasheet_Summary.pdf
>
> Yes, comments :-)
>
> First of all: are you going to store the Masterkey or the Passphrase /
> Keyfile which is used for key derivation?
> If you're going to store the master key, you don't need Luks at all,
> this would also be a solution for your detached-header problem.
>
> But....
>
> How do you want to realize the communication between the µC and you
> Linux Box? Over Uart? (Uart communication can _easily_ be sniffed, so be
> aware of that....)
If an attacker has access on that level, they can probaly just do
a memory-freeze attack or a fire-wire attack. Remember that
disk encryption does not protect data while the system is running
and has the data decrypted.
> Also don't forget to deactivate the JTAG interface. Otherwise the µC
> could get debugged... And don't forget to set the correct FUSE bits
> (disallow reading / writing from / to flash / EPROM memory, ....)
> And did you know, that CPU operations can be reconstructed by small
> fluctuations in current[1]? How do you want to solve this issue?
>
> How does the key get to the µC?
>
> Aah, almost forgot to mention: you talked about to use a RNG on your AVR
> to move the key around. RNG on AVR? From where do you get your entropy?
> I don't know much about this project, but maybe this helps you [2].
>
> There are *so* many traps... Do you really think this is a good idea?
I think this is mostly intended as a project to learn. As such
it should do well. But do not expet this to be secure against a
competent attacker.
Arno
> [1] http://en.wikipedia.org/wiki/Power_analysis
> [2] http://www.das-labor.org/wiki/AVR-Crypto-Lib //
> http://www.das-labor.org/wiki/AVR-Crypto-Lib#PRNGs
>
> Regards
> 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-29 14:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-28 9:15 [dm-crypt] Quick dm-crypt questions Cpp
2014-10-28 9:48 ` Milan Broz
2014-10-28 11:13 ` Arno Wagner
2014-10-29 9:24 ` Cpp
2014-10-29 10:33 ` Ralf Ramsauer
2014-10-29 14:59 ` Arno Wagner [this message]
2014-10-29 15:30 ` Ralf Ramsauer
2014-10-29 15:46 ` Ingo Schmitt
2014-10-29 16:21 ` Arno Wagner
2014-10-29 16:50 ` Milan Broz
2014-10-30 0:19 ` Sven Eschenberg
2014-10-29 15:53 ` Cpp
2014-10-29 16:30 ` Arno Wagner
2014-10-29 14:56 ` 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=20141029145900.GC11970@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.