DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Anton Mitterer <christoph.anton.mitterer@physik.uni-muenchen.de>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Hybrid drives
Date: Sat, 17 Jul 2010 13:10:17 +0200	[thread overview]
Message-ID: <1279365017.3289.26.camel@fermat.scientia.net> (raw)
In-Reply-To: <20100717094646.GA8391@fancy-poultry.org>

[-- Attachment #1: Type: text/plain, Size: 828 bytes --]

On Sat, 2010-07-17 at 11:46 +0200, Heinz Diehl wrote:
> As far as I understand, the SSD part of these hybrid drives is used as a
> cache, which doesn't loose its data when powered off. The disc itself is
> completely in encrypted state when off, but I'm quite curious what maybe
> could happen to the SSD part.
All is encrypted,.. expect those parts of the header which aren't
encrypted anyways.

The kernel encrypts everything at the (dm-crpyt) block layer,... "long"
before this goes out to hardware,... so the hardware never sees anything
that's unencrypted.


> is it completely covered by the additional crypto layer, or is there some
> internal transfer which happens "automatically" without being under
> control of the crypto layer?
As long as your CPU/bus is not hacked,... no ;)



Cheer,
Chris.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3387 bytes --]

  parent reply	other threads:[~2010-07-17 11:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-17  7:13 [dm-crypt] Hybrid drives Heinz Diehl
2010-07-17  7:17 ` Heinz Diehl
2010-07-17  7:58 ` Luca Berra
2010-07-17  9:46   ` Heinz Diehl
2010-07-17 11:05     ` Mikko Rauhala
2010-07-17 11:45       ` Heinz Diehl
2010-07-17 13:27         ` Sven Eschenberg
2010-07-17 11:10     ` Christoph Anton Mitterer [this message]
2010-07-17 10:57 ` Christoph Anton Mitterer
2010-07-18 17:01 ` 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=1279365017.3289.26.camel@fermat.scientia.net \
    --to=christoph.anton.mitterer@physik.uni-muenchen.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox