WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Zero RAM xm destroy

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Zero RAM xm destroy
From: Jonathan Tripathy <jonnyt@xxxxxxxxxxx>
Date: Sun, 18 Sep 2011 23:36:31 +0100
Delivery-date: Sun, 18 Sep 2011 15:37:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:6.0.2) Gecko/20110902 Thunderbird/6.0.2
Hi Everyone,

I've just had a "eureka" moment on how to prevent (or make harder) "cold boot attacks".

Am I correct in saying that when the admin issues "xm destroy <domID>" into the Dom0 shell, then 100% of the DomU ram is zero'ed immediately?

If so, could one use this as a security measure, in case server room intrusion is detected?

Thanks

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Zero RAM xm destroy, Jonathan Tripathy <=