From: Yves-Alexis Perez <corsac@debian.org>
To: Arno Wagner <arno@wagner.name>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] [dm-devel] dm-crypt performance
Date: Sun, 21 Apr 2013 22:38:36 +0200 [thread overview]
Message-ID: <1366576716.4048.13.camel@hidalgo> (raw)
In-Reply-To: <20130409184054.GA28430@tansi.org>
On mar., 2013-04-09 at 20:40 +0200, Arno Wagner wrote:
> > AES uses data-dependent lookup tables, on CPU with hyperthreding, the
> > second thread can observe L1 cache footprint done by the first thread and
> > get some information about data being encrypted...
>
> Yes, but that is not the only potential problem. For example, with
> Intel now implementing voltage regulators on the CPU, we may
> even see power-usage based leaks. If you are paranoid, constant
> time-contant-power implementations are the only solution. And
> while feasible, they are sloooooooowwwwww...
Note that on those CPUs AES should usually use AES-NI so timing attacks
using the cache should not be that relevant…
Regards,
--
Yves-Alexis
next prev parent reply other threads:[~2013-04-21 20:39 UTC|newest]
Thread overview: 81+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 3:47 dm-crypt performance Mikulas Patocka
2013-03-26 6:52 ` Christoph Hellwig
2013-03-26 12:27 ` [dm-crypt] [dm-devel] " Alasdair G Kergon
2013-03-26 12:27 ` Alasdair G Kergon
2013-03-26 20:05 ` [dm-crypt] " Milan Broz
2013-03-26 20:05 ` Milan Broz
2013-03-26 20:28 ` [dm-crypt] " Mike Snitzer
2013-03-26 20:28 ` Mike Snitzer
2013-03-26 20:58 ` [dm-crypt] " Milan Broz
2013-03-26 20:58 ` Milan Broz
2013-03-28 18:53 ` [dm-crypt] " Tejun Heo
2013-03-28 18:53 ` Tejun Heo
2013-03-28 19:33 ` [dm-crypt] " Vivek Goyal
2013-03-28 19:33 ` Vivek Goyal
2013-03-28 19:44 ` [dm-crypt] " Tejun Heo
2013-03-28 19:44 ` Tejun Heo
2013-03-28 20:38 ` [dm-crypt] " Vivek Goyal
2013-03-28 20:38 ` Vivek Goyal
2013-03-28 20:45 ` Tejun Heo
2013-04-09 17:51 ` [dm-crypt] dm-crypt parallelization patches Mikulas Patocka
2013-04-09 17:51 ` Mikulas Patocka
2013-04-09 17:57 ` Tejun Heo
2013-04-09 18:08 ` [dm-crypt] " Mikulas Patocka
2013-04-09 18:08 ` Mikulas Patocka
2013-04-09 18:10 ` Tejun Heo
2013-04-09 18:42 ` [dm-crypt] " Vivek Goyal
2013-04-09 18:42 ` Vivek Goyal
2013-04-09 18:57 ` Tejun Heo
2013-04-09 19:13 ` [dm-crypt] " Vivek Goyal
2013-04-09 19:13 ` Vivek Goyal
2013-04-09 19:42 ` [dm-crypt] " Mikulas Patocka
2013-04-09 19:42 ` Mikulas Patocka
2013-04-09 19:52 ` Tejun Heo
2013-04-09 20:32 ` [dm-crypt] " Mikulas Patocka
2013-04-09 20:32 ` Mikulas Patocka
2013-04-09 21:02 ` Tejun Heo
2013-04-09 21:03 ` Tejun Heo
2013-04-09 21:07 ` [dm-crypt] " Vivek Goyal
2013-04-09 21:07 ` Vivek Goyal
2013-04-09 21:18 ` [dm-crypt] " Mikulas Patocka
2013-04-09 21:18 ` Mikulas Patocka
2013-04-10 19:24 ` [dm-crypt] " Vivek Goyal
2013-04-10 19:24 ` Vivek Goyal
2013-04-10 23:42 ` [dm-crypt] [PATCH] make dm and dm-crypt forward cgroup context (was: dm-crypt parallelization patches) Mikulas Patocka
2013-04-10 23:42 ` Mikulas Patocka
2013-04-10 23:50 ` Tejun Heo
2013-04-11 19:49 ` [dm-crypt] [PATCH v2] " Mikulas Patocka
2013-04-11 19:49 ` Mikulas Patocka
2013-04-11 19:52 ` Tejun Heo
2013-04-11 20:00 ` Tejun Heo
2013-04-12 0:06 ` [dm-crypt] " Mikulas Patocka
2013-04-12 0:06 ` Mikulas Patocka
2013-04-12 0:22 ` Tejun Heo
2013-04-12 5:59 ` [dm-crypt] [PATCH v2] make dm and dm-crypt forward cgroup context Milan Broz
2013-04-12 5:59 ` Milan Broz
2013-04-12 18:17 ` [dm-crypt] [PATCH v2] make dm and dm-crypt forward cgroup context (was: dm-crypt parallelization patches) Mikulas Patocka
2013-04-12 18:17 ` Mikulas Patocka
2013-04-12 18:01 ` [dm-crypt] " Mikulas Patocka
2013-04-12 18:01 ` Mikulas Patocka
2013-04-12 18:29 ` Tejun Heo
2013-04-15 13:02 ` [dm-crypt] " Mikulas Patocka
2013-04-15 13:02 ` Mikulas Patocka
2013-04-16 17:24 ` Tejun Heo
2013-04-16 19:41 ` [dm-crypt] " Mikulas Patocka
2013-04-16 19:41 ` Mikulas Patocka
2013-04-18 16:47 ` [dm-crypt] " Mike Snitzer
2013-04-18 16:47 ` Mike Snitzer
2013-04-18 17:03 ` Tejun Heo
2013-05-22 18:50 ` [dm-crypt] " Mike Snitzer
2013-05-22 18:50 ` Mike Snitzer
2013-05-22 19:48 ` Tejun Heo
2013-04-09 18:36 ` [dm-crypt] dm-crypt parallelization patches Vivek Goyal
2013-04-09 18:36 ` Vivek Goyal
2013-04-09 18:08 ` [dm-crypt] [dm-devel] dm-crypt performance Mikulas Patocka
2013-04-09 18:08 ` Mikulas Patocka
2013-04-09 18:08 ` Mikulas Patocka
2013-04-09 18:40 ` [dm-crypt] " Arno Wagner
2013-04-21 20:38 ` Yves-Alexis Perez [this message]
2013-04-22 2:28 ` Arno Wagner
2013-04-09 18:59 ` Milan Broz
2013-04-09 18:59 ` Milan Broz
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=1366576716.4048.13.camel@hidalgo \
--to=corsac@debian.org \
--cc=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.