From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <peter@alpha-force.net>
Received: from citadel.alpha-force.net (citadel.alpha-force.net
 [193.95.228.232])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mail.saout.de (Postfix) with ESMTPS
 for <dm-crypt@saout.de>; Mon, 14 Feb 2011 14:13:05 +0100 (CET)
Received: from localhost ([127.0.0.1]) by citadel.alpha-force.net
 for dm-crypt@saout.de; Mon, 14 Feb 2011 14:03:01 +0100
From: Peter <peter@alpha-force.net>
Message-ID: <20110214140301.b373bee9@citadel.alpha-force.net>
Date: Mon, 14 Feb 2011 14:03:01 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: [dm-crypt] Memory location of the encryption key
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt@saout.de

Hey!

I've been reading Gutmann's paper on data remanence, which says that if =
some data is kept in the same memory location for very little time (1 se=
cond), the possibility for recovery of this data is very low, because th=
e data had not yet had the time to change the relevant physical properti=
es used in cold boot attacks. My question is, does dm-crypt change the m=
emory location of encryption key every second=3F Does dm-crypt rewrite t=
he memory location of the key when removing an active mapping=3F What ot=
her cold boot attack mitigation techniques the dm-crypt does=3F

Happy day,
Peter