All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter <peter@alpha-force.net>
To: dm-crypt@saout.de
Subject: [dm-crypt] Memory location of the encryption key
Date: Mon, 14 Feb 2011 14:03:01 +0100	[thread overview]
Message-ID: <20110214140301.b373bee9@citadel.alpha-force.net> (raw)

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 second), the possibility for recovery of this data is very low, because the data had not yet had the time to change the relevant physical properties used in cold boot attacks. My question is, does dm-crypt change the memory location of encryption key every second? Does dm-crypt rewrite the memory location of the key when removing an active mapping? What other cold boot attack mitigation techniques the dm-crypt does?

Happy day,
Peter

             reply	other threads:[~2011-02-14 13:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14 13:03 Peter [this message]
2011-02-15  9:54 ` [dm-crypt] Memory location of the encryption key Milan Broz
2011-02-15 15:42 ` Arno Wagner
  -- strict thread matches above, loose matches on Subject: below --
2011-03-14 22:16 Hanno Foest
2011-03-14 23:15 ` Arno Wagner

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=20110214140301.b373bee9@citadel.alpha-force.net \
    --to=peter@alpha-force.net \
    --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.