All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt@stachelkaktus.net, dm-crypt@saout.de
Subject: Re: [dm-crypt] luksSuspend for plain dm-crypt
Date: Tue, 29 Aug 2017 15:17:25 +0200	[thread overview]
Message-ID: <3eb006d0-ce2c-7399-36a0-70a422c4f44c@gmail.com> (raw)
In-Reply-To: <98dd7f23-31c3-1935-2524-9f58a14234ea@stachelkaktus.net>

On 08/29/2017 02:42 PM, dm-crypt@stachelkaktus.net wrote:
> 
> That sounds interesting, but I'm not sure if it will help. I try to kill
> the erase the key before I suspend on ram so that cold boot attack don't
> work here. If its in the kernel keyring It should be still possible to
> find it in the memory. Or have I misread that keyring conzept?

Yes, you are correct.

For this key (volume key) it can be wiped after dm-crypt device
is activated, the reaon to use keyring is that the key is no longer included
in dm-ioctl and dm-crypt no longer need to keep the key in its internal structures.

Now during dm-crypt device lifetime (except luksSuspend) the key is in memory
in several places: dm-crypt struct and then in crypto API engine - usually multiple
times (per CPU, depends on crypto module implementation).

Dm-crypt wipe command should wipe all these keys.

Milan

      reply	other threads:[~2017-08-29 13:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-29  9:37 [dm-crypt] luksSuspend for plain dm-crypt dm-crypt
2017-08-29 10:19 ` Milan Broz
2017-08-29 12:42   ` dm-crypt
2017-08-29 13:17     ` Milan Broz [this message]

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=3eb006d0-ce2c-7399-36a0-70a422c4f44c@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=dm-crypt@stachelkaktus.net \
    /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.