From: Fruhwirth Clemens <clemens@endorphin.org>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Initial Vector Fix for loop.c.
Date: Fri, 20 Jun 2003 12:14:52 +0200 [thread overview]
Message-ID: <20030620101452.GA2233@ghanima.endorphin.org> (raw)
In-Reply-To: <p73u1al3xlw.fsf@oldwotan.suse.de>
[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]
On Fri, Jun 20, 2003 at 11:30:03AM +0200, Andi Kleen wrote:
> Fruhwirth Clemens <clemens-dated-1056963973.bf26@endorphin.org> writes:
>
> > So go for it. Fix it before 2.6.x is out and we're stuck with this crap
> > again.
>
> This will break existing crypto loop installations, making
> the existing encrypted image unreadable. After all this is Linux
> here, not HackOS where you can break user file system formats at will.
> The only way to implement this is with a new flag that is set by losetup
> and keep the old behaviour by default.
There is no cryptoloop installation which is affected by this. Read my mail
properly. Every cryptoloop setup out there uses loop-AES or kerneli's
patch-int. And both fixed this issue a _long_ time ago. (Have a look at
the linux-crypto archives of 2001).
Adam Richter's version of loop.c which is in his ygg tree is quite nice,
but his changes are HUGE. Nobody is going to split them up in small patches.
Again: _no_ userbase is affected by this change. Every userbase which
could have ever been affected has done the fix for itself.
Clemens
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2003-06-20 10:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030620090612.GA1322@ghanima.endorphin.org.suse.lists.linux.kernel>
2003-06-20 9:30 ` [PATCH] Initial Vector Fix for loop.c Andi Kleen
2003-06-20 10:14 ` Fruhwirth Clemens [this message]
2003-06-20 10:24 ` Andi Kleen
2003-06-20 10:33 ` Fruhwirth Clemens
2003-06-20 10:35 ` Jörn Engel
2003-06-20 10:49 ` Andi Kleen
2003-06-20 10:52 ` Andi Kleen
2003-06-20 11:15 ` Fruhwirth Clemens
2003-06-20 10:51 ` Fruhwirth Clemens
2003-06-20 11:03 ` Jörn Engel
2003-06-21 2:18 ` Jan Rychter
2003-06-24 18:22 ` Bill Davidsen
2003-06-20 17:56 ` Andrew Morton
2003-06-20 18:14 ` David S. Miller
2003-06-20 19:04 ` Andries Brouwer
2003-06-20 13:38 Fruhwirth Clemens
-- strict thread matches above, loose matches on Subject: below --
2003-06-20 9:06 Fruhwirth Clemens
2003-06-20 9:23 ` Andrew Morton
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=20030620101452.GA2233@ghanima.endorphin.org \
--to=clemens@endorphin.org \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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.