Re: international crypto patch as non-kernel-patch...

[Andrew McGuinness <andrew_mcguinness@bigfoot.com>]

Quoting Andi Kleen <ak@suse.de>:

> On Sat, Apr 21, 2001 at 04:05:36PM -0700, Dan Hollis wrote:
> > On Sun, 22 Apr 2001, Herbert Valerio Riedel wrote:
> > > there's only one issue I'm fighting with... that damned broken IV
> > > calculation... :-/
> > 
> > Is this why 2.4 blowfish crypto won't work with 2.2 blowfish crypto?
> 
> I don't know anything about the "blowfish crypto" you use, the following
> is a generic statement.
> 
> The encrypted on disk files are incompatible if the crypto module used
> the 2.2 IV directly. You can write a 2.4 crypt module that can still
> read 2.2 files, but it needs some changes -- it needs to manually remap
> the relative numbers via bmap to absolute. 2.2 passed absolute block
> numbers, 
> which was really broken, 2.4 switched to relative logical block numbers
> (which still have some problems, but are not too bad).
> 

That's not quite right, is it?  2.2 had a compile-time CONFIG_ option to
use relative block numbers, which I thought most people used.

--
Andrew McGuinness     Luton, UK        andrew_mcguinness@bigfoot.com

Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/