All of lore.kernel.org
 help / color / mirror / Atom feed
From: Molle Bestefich <molle.bestefich@gmail.com>
To: Bjorn Andersson <bjorn.andersson@silversmedjan.se>
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: dm-crypt userland key patch
Date: Fri, 15 Apr 2005 23:48:09 +0200	[thread overview]
Message-ID: <62b0912f05041514485f38f872@mail.gmail.com> (raw)
In-Reply-To: <20050414141459.6d521f67@emotpin>

Bjorn Andersson wrote:
> > > Patch to the dm-crypt module so that it hides the crypto-key from
> > > userland. (dmsetup table)
> >
> > Does it also overwrite the key in memory when unloading dm-crypt, make
> > sure that the memory is pinned so the key doesn't leak to swap, unload
> > the key before a 'hibernate', and that sort of stuff?
>
> No, this does only report a key of zeros when the status is requested.
> 
> The unloading thing is no problem to fix, but how should the
> 'hibernate' thing work? When you resume after a 'hibernate' you probably
> expect that the device is there, especially if it's on the root
> partition. But I clearly see your point.

*Scratches head*, I'd expect the default to be "doing the safe thing",
eg. picking up on hibernation and nuking the key (disabling any crypto
devices).  If there's a lean no-hassles user interface to get the
password entered and the devices up again when the machine is resumed,
I'd imagine most users to be happy about it, especially when they're
told that it's done to protect their encrypted data?

There might be a few people annoyed by it?  Or there might even be
some obscure technical reason why you'd want your keys to survive
hibernation..  For those cases there could be an option to disable
"hibernation protection" or what not.

Dunno, IANA expert :-o.

      reply	other threads:[~2005-04-15 21:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-13 17:41 Multipath Statistics Lan
2005-04-13 21:58 ` dm-crypt userland key patch Bjorn Andersson
2005-04-14  7:13   ` Molle Bestefich
2005-04-14 12:14     ` Bjorn Andersson
2005-04-15 21:48       ` Molle Bestefich [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=62b0912f05041514485f38f872@mail.gmail.com \
    --to=molle.bestefich@gmail.com \
    --cc=bjorn.andersson@silversmedjan.se \
    --cc=dm-devel@redhat.com \
    /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.