From: Shawn Willden <shawn-lkml@willden.org>
To: Mark Borgerding <mark@borgerding.net>, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: AES cryptoloop corruption under recent -mm kernels
Date: Sat, 17 Jan 2004 13:39:36 -0700 [thread overview]
Message-ID: <200401171339.43800.shawn-lkml@willden.org> (raw)
In-Reply-To: <40081AF0.5060907@borgerding.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Friday 16 January 2004 10:10 am, Mark Borgerding wrote:
> Thinking of it another way, this is equivalent to CBC mode having two
> IVs: the first one being the sector number, the second a block of
> zeros.\r
Even simpler, conceptually, it's equivalent to prepending a block of zeros
to every sector prior to encrypting.
I'm not one to argue with Eli Biham (even second or third-hand), but it's
really hard to see how this makes any difference at all.
Shawn.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFACZ2Op1Ep1JptinARAkzhAJ46cOO7JS0ccoid7aer7p+nZ1K2DQCbB3In
JeIsagKKEsBaRiEZY+sElZ8=
=ISsB
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-01-17 20:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 20:36 Jim Faulkner
2004-01-14 20:41 ` Jim Faulkner
2004-01-14 20:52 ` Andrew Morton
2004-01-14 23:30 ` Jim Faulkner
2004-01-15 2:44 ` Matthias Hentges
2004-01-15 16:57 ` Jari Ruusu
2004-01-15 17:24 ` Jim Faulkner
2004-01-15 20:33 ` Jari Ruusu
2004-01-15 22:59 ` Hans Reiser
2004-01-16 14:21 ` Mark Borgerding
2004-01-16 15:42 ` James Morris
2004-01-16 17:10 ` Mark Borgerding
2004-01-17 2:47 ` David Wagner
2004-01-17 16:13 ` Mark Borgerding
2004-01-17 20:39 ` Shawn Willden [this message]
[not found] ` <4007EBDA.2060308@borgerding.net>
[not found] ` <4007F79C.80A5DE72@users.sourceforge.net>
[not found] ` <400818AA.9080009@borgerding.net>
2004-01-16 21:43 ` Jari Ruusu
2004-01-15 18:16 ` James Morris
2004-02-01 17:19 ` Pasi Kärkkäinen
2004-02-01 19:40 ` markus reichelt
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=200401171339.43800.shawn-lkml@willden.org \
--to=shawn-lkml@willden.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@borgerding.net \
/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
all inboxes | Powered by JetHome®