From: Christoph Anton Mitterer <christoph.anton.mitterer@physik.uni-muenchen.de>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Efficacy of xts over 1TB
Date: Mon, 26 Jul 2010 23:31:56 +0200 [thread overview]
Message-ID: <1280179916.3266.131.camel@fermat.scientia.net> (raw)
In-Reply-To: <20100726210741.GC24052@tansi.org>
[-- Attachment #1: Type: text/plain, Size: 791 bytes --]
On Mon, 2010-07-26 at 23:07 +0200, Arno Wagner wrote:
> > So you guess the the 1TB limit could be actually a "don't have blocks
> > larger than 1TB" limit?!
> Actually, it is the "plain" implementation that causes a 2TB limit
> because of repeating IVs. XTS has a block size limit, at 2^20 bits,
> (I think) but it is a recommended limit. As 512 bytes we are well
> below that :-)
So you mean we have two limits?
1) The limit related to the IVs that we get from "plain" after 32bit 512
byte blocks, or that we would get from plain64 on a Zettabyte device.
2) Another limit, on the maximum block size (which was misconceived as a
maximum filesystem size) that can be securely used which is that 1TB
thingy?
However we should never hit that one too?!
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3387 bytes --]
next prev parent reply other threads:[~2010-07-26 21:31 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 21:07 [dm-crypt] Efficacy of xts over 1TB Arno Wagner
2010-07-26 21:31 ` Christoph Anton Mitterer [this message]
2010-07-26 21:45 ` Arno Wagner
2010-07-26 21:42 ` Christoph Anton Mitterer
2010-07-26 22:55 ` Arno Wagner
2010-07-26 23:42 ` Mario 'BitKoenig' Holbe
2010-07-27 10:21 ` Arno Wagner
2010-08-15 17:26 ` Uwe Menges
2010-08-15 22:10 ` Arno Wagner
2010-08-16 11:44 ` Mario 'BitKoenig' Holbe
2010-08-16 12:39 ` Arno Wagner
2010-08-16 12:55 ` octane indice
2010-08-16 14:21 ` Arno Wagner
2010-08-21 20:45 ` Christoph Anton Mitterer
2010-08-21 23:14 ` Arno Wagner
2010-08-22 0:46 ` Christoph Anton Mitterer
-- strict thread matches above, loose matches on Subject: below --
2010-07-25 22:25 Ietf Nist
2010-07-25 22:41 ` Christoph Anton Mitterer
2010-07-22 14:57 David Santamaría Rogado
2010-07-25 10:34 ` Arno Wagner
2010-07-25 11:18 ` Christoph Anton Mitterer
2010-07-25 12:29 ` Heinz Diehl
2010-07-25 12:25 ` Milan Broz
2010-07-25 13:14 ` Christoph Anton Mitterer
2010-07-25 13:52 ` Milan Broz
2010-07-25 22:37 ` Christoph Anton Mitterer
2010-07-26 0:14 ` Milan Broz
2010-07-26 20:38 ` Christoph Anton Mitterer
2010-07-26 8:53 ` Arno Wagner
2010-07-26 20:47 ` Christoph Anton Mitterer
2010-07-26 21:01 ` Arno Wagner
2010-07-26 21:28 ` Christoph Anton Mitterer
2010-07-26 21:35 ` Arno Wagner
2010-07-25 22:52 ` Christoph Anton Mitterer
2010-07-26 9:42 ` Mario 'BitKoenig' Holbe
2010-07-26 18:09 ` Arno Wagner
2010-07-25 15:32 ` Arno Wagner
2010-07-25 22:48 ` Christoph Anton Mitterer
2010-07-25 23:42 ` Milan Broz
2010-07-26 18:35 ` Christoph Anton Mitterer
2010-07-25 15:28 ` Arno Wagner
2010-07-25 18:11 ` Milan Broz
2010-07-26 9:04 ` Mario 'BitKoenig' Holbe
2010-07-27 18:21 ` Christoph Anton Mitterer
2010-07-27 21:02 ` Mario 'BitKoenig' Holbe
2010-07-26 9:17 ` Mario 'BitKoenig' Holbe
2010-07-27 18:42 ` David Santamaría Rogado
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=1280179916.3266.131.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 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.