From: Mike Fedyk <mfedyk@matchmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Jean-Luc Cooke <jlcooke@certainkey.com>,
dean gaudet <dean-list-linux-kernel@arctic.org>,
James Morris <jmorris@redhat.com>,
Christophe Saout <christophe@saout.de>,
Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: DM for detecting bad disks was: dm-crypt, new IV and standards
Date: Sat, 06 Mar 2004 20:14:42 -0800 [thread overview]
Message-ID: <404AA1B2.4090500@matchmail.com> (raw)
In-Reply-To: <20040304150836.GE531@openzaurus.ucw.cz>
Pavel Machek wrote:
> Hi!
>
>
>>>>Well, CTR mode is not recommended for encrypted file systems because it is very
>>>>easy to corrupt single bits, bytes, blocks, etc without an integrity check.
>>>>If we add a MAC, then any mode of operation except ECB can be used for
>>>>encrypted file systems.
>>>
>>>what does "easy to corrupt" mean? i haven't really seen disks generate
>>>bit errors ever. this MAC means you'll need to write integrity data for
>>>every real write. that really doesn't seem worth it...
>>
>>The difference between "_1,000,000" and "_8,000,000" is 1 bit. If an
>>attacker knew enough about the layout of the filesystem (modify times on blocks,
>>etc) they could flip a single bit and change your _1Mil purchase order
>>approved by your boss to a _8Mil order.
>
>
> Hmm... long time ago I created crc loop device to catch
> faulty disks. If cryptoloop can do that for me... very good!
Yes, a crc, or some other very low overhead DM target would be great for
this. I haven't looked at DM too much. :( Does it already have
something like this already?
prev parent reply other threads:[~2004-03-07 4:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 22:06 dm-crypt, new IV and standards Carl-Daniel Hailfinger
2004-02-19 22:20 ` Christophe Saout
2004-02-20 17:22 ` Jean-Luc Cooke
2004-02-20 21:26 ` James Morris
2004-02-20 21:52 ` 2.6.3 adaptec I2O will not compile David Lang
2004-02-25 16:25 ` Adrian Bunk
2004-02-26 8:02 ` Jaco Kroon
2004-02-26 8:08 ` David Lang
2004-02-26 9:28 ` Jaco Kroon
2004-02-26 10:24 ` David Lang
2004-02-21 0:31 ` dm-crypt, new IV and standards Carl-Daniel Hailfinger
2004-02-21 16:48 ` Jean-Luc Cooke
2004-02-21 17:36 ` Jean-Luc Cooke
2004-02-21 19:01 ` Andreas Jellinghaus
2004-03-03 8:35 ` dean gaudet
2004-03-03 15:06 ` Jean-Luc Cooke
2004-03-03 21:40 ` David Wagner
2004-03-08 19:58 ` Jean-Luc Cooke
2004-03-04 1:48 ` dean gaudet
2004-03-04 13:24 ` Jean-Luc Cooke
2004-03-04 17:44 ` David Wagner
2004-03-05 1:19 ` dean gaudet
2004-03-05 2:14 ` Jean-Luc Cooke
2004-03-04 15:08 ` Pavel Machek
2004-03-07 4:14 ` Mike Fedyk [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=404AA1B2.4090500@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=akpm@osdl.org \
--cc=c-d.hailfinger.kernel.2004@gmx.net \
--cc=christophe@saout.de \
--cc=dean-list-linux-kernel@arctic.org \
--cc=jlcooke@certainkey.com \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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