TRESOR still leaves all the code and data exposed in memory. You can modify the code that's being executed in order to divulge the contents of the debug registe

TRESOR still leaves all the code and data exposed in memory. You can modify the code that's being executed in order to divulge the contents of the debug registers. We're working on solving the malicious device and cold boot problem at PrivateCore. To do so, we're encrypting all of main memory and keeping plaintext state in the L3 cache. Here's a resource page with links to the TRESOR paper and other resources: http://privatecore.com/resources-overview/physical-memory-attacks/ http://privatecore.com/resources-overview/physical-memory-at...