All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <mbroz@redhat.com>
To: octane indice <octane@alinto.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] using a salt for encrypting blocks
Date: Tue, 28 Dec 2010 12:03:26 +0100	[thread overview]
Message-ID: <4D19C3FE.1000100@redhat.com> (raw)
In-Reply-To: <1293524963.4d199fe3b7cb1@www.inmano.com>

On 12/28/2010 09:29 AM, octane indice wrote:
> En réponse à Arno Wagner <arno@wagner.name> :
>> The anzwer is actually no. As changed information has to be 
>> written to diek, an attacker can allways tell when a sector 
>> is changed.
> 
> My idea is to cipher _all_ blocks by changing the salt.

You forgot one fundamental thing.

If an attacker can do snapshots in time (IOW he can read the cipher
text device after user performed some changes) he has either
physical access to the system or he has administrator permissions.

This allows more powerfull attacks already (installing keylogger,
modifying kernel, bios, ...).

If an attacker has such access nothing will help you.
The chain is weaker somewhere else here.

> not so much, depending on how much data you cipher.
> I use files of less than 100Mbytes and cipher them. On
> close, a full recipher wouldn't take long.

Then use encryption on filesystem level (e.g. with CTR mode, iow
stream mode) and not sector level block device encryption.

Milan

  reply	other threads:[~2010-12-28 11:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-27 16:10 [dm-crypt] using a salt for encrypting blocks octane indice
2010-12-27 21:52 ` Arno Wagner
2010-12-28  8:29   ` octane indice
2010-12-28 11:03     ` Milan Broz [this message]
2010-12-28 14:05       ` octane indice
2010-12-28 19:49         ` Milan Broz
2010-12-30 10:11           ` octane indice
2010-12-30 12:27             ` Arno Wagner
2010-12-28 13:32     ` Arno Wagner
2010-12-28 14:23       ` octane indice

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=4D19C3FE.1000100@redhat.com \
    --to=mbroz@redhat.com \
    --cc=dm-crypt@saout.de \
    --cc=octane@alinto.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.