All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Quick dm-crypt questions
Date: Wed, 29 Oct 2014 17:50:20 +0100	[thread overview]
Message-ID: <54511ACC.7080708@gmail.com> (raw)
In-Reply-To: <20141029162128.GD11970@tansi.org>

On 10/29/2014 05:21 PM, Arno Wagner wrote:
> FAQ Item 6.10 should also apply to AES-NI, AFAIK. 
> I do not have an AES-NI capable system though to
> thest that.

I think AES-NI can help with some (cache) timing attack but
not with Cold boot.

> I think this whole idea of storing keys in cache
> was some demo at some conference, but is not fit for
> practical deployment, as CPUs are too differtent.

If you mean idea of frozen-cache, it's impact to performance is huge.

There is also TRESOR and loop-amnesia which tries
fix the cold boot problem.

(Just Google for frozen cache, tresor+aes or loop-amnesia for more info.)

But all is x86_64 only and there is a lot of problems
(the first one is that it is not in upstream kernel:-)

(And dmcrypt has still one copy of key in its structs,
so deploying such solution requires some changes here as well,
not trivial because of device-mapper table logic.)

Milan

  reply	other threads:[~2014-10-29 16:50 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
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 [this message]
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=54511ACC.7080708@gmail.com \
    --to=gmazyland@gmail.com \
    --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.