linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* RAM encryption and key storing in CPU
@ 2015-05-26 15:21 someone called
  2015-05-26 18:32 ` Richard Weinberger
  0 siblings, 1 reply; 2+ messages in thread
From: someone called @ 2015-05-26 15:21 UTC (permalink / raw)
  To: linux-kernel

Hello,

==========
Problem:

Everything is stored in plaintext in the Memory.

So if although full disc encryption is used on an ex.: Linux Desktop, it is possible to copy the content of the memory, while the notebook was on suspend or it was running:

https://citp.princeton.edu/research/memory/media/

==========
Solution:

Can we (optionally*) encrypt the content of the memory and store the key for decryption in the CPU to avoid these kind of attacks in general?

Example patches (I am NOT related to them): 

https://www1.informatik.uni-erlangen.de/tresor

Is this solution already in the Linux kernel? If yes, how can a Linux enduser turn it on? If no, how can we get the code/idea in the mainline? What are the arguments against it?

*if someone would want to harden it's Linux Desktop (since notebooks could be stolen..) it could turn on this feature to avoid a policy to always turn off the notebook while not using it.

Thank you for your comments.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: RAM encryption and key storing in CPU
  2015-05-26 15:21 RAM encryption and key storing in CPU someone called
@ 2015-05-26 18:32 ` Richard Weinberger
  0 siblings, 0 replies; 2+ messages in thread
From: Richard Weinberger @ 2015-05-26 18:32 UTC (permalink / raw)
  To: someone called; +Cc: LKML

On Tue, May 26, 2015 at 5:21 PM, someone called
<someonecalled@safe-mail.net> wrote:
> https://www1.informatik.uni-erlangen.de/tresor
>
> Is this solution already in the Linux kernel? If yes, how can a Linux enduser turn it on? If no, how can we get the code/idea in the mainline? What are the arguments against it?

No, these patches are not mainline.
IMHO such solutions paper over the real problem. Adding new layers won't help.
If we store keys in CPU registers, secret agencies will (or have
already) develop tools to dump them too.

-- 
Thanks,
//richard

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-05-26 18:32 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-05-26 15:21 RAM encryption and key storing in CPU someone called
2015-05-26 18:32 ` Richard Weinberger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).