All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Encrypted Raid1 or Raid 1 of encrypted devices?
Date: Thu, 14 Jul 2011 13:01:01 +0200	[thread overview]
Message-ID: <20110714110101.GA13900@tansi.org> (raw)
In-Reply-To: <4E1E89FD.80704@gmx.com>

On Thu, Jul 14, 2011 at 09:17:33AM +0300, Yaron Sheffer wrote:
> Hi Arno,
> 
> I agree that most practical considerations point towards encrypt-over-RAID.
> 
> But in fact from a security point of view, it seems to me the
> situation is reversed. Looking at RAID-over-encryption, I disagree
> that having the same plaintext encrypted over multiple keys is a
> concern with modern ciphers. 

You have to take into account that this is a non-moving target, 
i.e. disk encryption. Still, the security-loss should be small.

> The real concern with most full disk
> encryption (and dm-crypt in particular) is integrity protection: the
> ability of an attacker to change the ciphertext undetected. This
> ability is greatly hampered when the attacker needs to coordinate
> the attacks on two mirrored blocks, otherwise the two copies would
> not be consistent.

You possibly think that not having access to the RAID superblock
(as it is encrypted) will make this manipulation much harder. 
My take is that as soon as the attacker is on your device, he/she
can patch cryptsetup and then waut until you enter your passphrase.
Disk-encryption really only protects against attackers that 
only have access once and not while you are working on or opening
the device. This applies mostly to the case whre your device
is stolen. I don't agree that integrity protection has any
role in ordinary scenarios. And if you have a special scenario
where it plays a role, you should not use LUKS or dm-crypt anyways,
as it does not offer integrity protection, plain and simple.

> I haven't researched all figerprinting attacks and the interaction
> with various ways of generating IVs, so my intuition may still be
> proven wrong.

I thing your risk model is wrong. Basically it covers attacks
were the attacker has access to only the storage and at the same 
time can actually do something serious with data manipulation.
That is a rather unlikely scenario for disk encryption. Note that
for communication encryption, this is a real and valid scenario.

Arno
-- 
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name 
GnuPG:  ID: 1E25338F  FP: 0C30 5782 9D93 F785 E79C  0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans

If it's in the news, don't worry about it.  The very definition of 
"news" is "something that hardly ever happens." -- Bruce Schneier 

  reply	other threads:[~2011-07-14 11:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.6.1310512453.3639.dm-crypt@saout.de>
2011-07-14  6:17 ` [dm-crypt] Encrypted Raid1 or Raid 1 of encrypted devices? Yaron Sheffer
2011-07-14 11:01   ` Arno Wagner [this message]
2011-07-14 11:41     ` Roscoe
2011-07-14 13:42       ` Arno Wagner
2011-07-11 22:03 Laurence Darby
2011-07-12 11:32 ` Jorge Fábregas
2011-07-12 12:10   ` Milan Broz
2011-07-12 12:31     ` Arno Wagner
2011-07-12 23:14       ` Laurence Darby
2011-07-12 12:20 ` 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=20110714110101.GA13900@tansi.org \
    --to=arno@wagner.name \
    --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.