![]() | |||||||||||||
Messages in this thread |
On Fri, Jun 20, 2003 at 12:14:52PM +0200, Fruhwirth Clemens wrote: > 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 That's completely wrong. I know of several independent implementation and installations. > Again: _no_ userbase is affected by this change. Every userbase which > could have ever been affected has done the fix for itself. That's also incorrect. -Andi - 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/ | ||||||||||||
| Last update: 2005-03-22 12:36 [from the cache] ©2003-2008 | |||||||||||||