From: Milan Broz <gmazyland@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Fwd: Practical malleability attack against CBC-Encrypted LUKS partitions
Date: Mon, 23 Dec 2013 08:56:29 +0100 [thread overview]
Message-ID: <52B7ECAD.5080202@gmail.com> (raw)
In-Reply-To: <20131222230724.GA1991@phobos.panopticism.net>
On 12/23/2013 12:07 AM, /dev/ph0b0s wrote:
> On 12/22, Milan Broz wrote:
>> Below is very nice example of another "Evil maid" type attacks,
>> here directly applied to LUKS CBC disks.
>>
>> I think it clearly shows known rule:
>> If you let your machine out of your sight, it is no longer your machine.
>>
>> What is important (and blog mentions it)
>>
>> "It has already been known for a long time that CBC does not prevent
>> a malleability attack (targeted manipulation of encrypted data) given
>> that the attacker can modify the ciphertext and knows the corresponding
>> plaintext as well."
>
> Even more important, in this particular case, is that this "practical
> malleability attack" isn't actually very practical at all:
>
> "In the following I assume that we already have access to the
> original plaintext and the ciphertext of one file on the system and
> that we want to do our manipulations in this file:"
Sure. On the other side, if you have "golden image" and all your
company laptops are encrypted using the same plaintext in the beginning,
this could be possible.
Anyway, I do not think this attack is anything new - it is just real
application of known facts on the one specific case.
But it is worth to mention here.
...
>> BTW blog doesn't mention that CBC is no longer default mode for cryptsetup
>> and was replaced by XTS mode.
>
> The original post to f-d [0] that you forwarded does mention this:
I meant this part:
"When manually creating LUKS partitions, you should make sure to use XTS
instead of CBC (which is still the default when running cryptsetup
luksFormat without a cipher specification):"
It is not default since 1.6.0 upstream version (and it was configurable
even before for distro maintainers).
Milan
next prev parent reply other threads:[~2013-12-23 7:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAH8yC8=i5x0My2ZMJrj8oikE8t6vQUGUX8WP2PC1uhO6HS=Mbw@mail.gmail.com>
2013-12-22 22:06 ` [dm-crypt] Fwd: Practical malleability attack against CBC-Encrypted LUKS partitions Milan Broz
2013-12-22 23:07 ` /dev/ph0b0s
2013-12-23 7:56 ` Milan Broz [this message]
2013-12-23 11:13 ` 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=52B7ECAD.5080202@gmail.com \
--to=gmazyland@gmail.com \
--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.