Messages in this thread | | | Date | Tue, 26 Feb 2002 22:58:25 +0200 | From | Jari Ruusu <> | Subject | Re: loop under 2.2.20 - relative block support? |
| |
mailerror@hushmail.com wrote: > On Mon, 25 Feb 2002 20:41:25 +0200, Jari Ruusu <jari.ruusu@pp.inet.fi> wrote: > >If you can move original (unmodified) loop file to same block size, same > >kernel version, then yes. If you mounted it rw, then your "time bomb" > >exploded on your face. > > > > Okay, my files are fine then, since the files were burned on cd right after I > created them. > > Is this still a problem with the 2.4 loop device? In your patch for 2.4.16 > I noticed that the IV calculation is independent from the underlying block > size. That alone would be enough to make me switch over from 2.2 ;-)
Recent versions of cryptoapi do 512 byte IV as do all versions of loop-AES (maintained by me, http://loop-aes.sourceforge.net/). If you want to keep using 2.2 kernels or want to use distro vendor kernels, loop-AES is better choice as it works with all kernels and has more up to date loop fixes than cryptoapi.
Regards, Jari Ruusu <jari.ruusu@pp.inet.fi> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |