![]() | |||||||||||||
Messages in this thread |
On Fri, 20 Jun 2003, Andi Kleen wrote: > On Fri, Jun 20, 2003 at 12:14:52PM +0200, Fruhwirth Clemens wrote: > > 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. Could you point to these implementations? > > > 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. I think the point is that if moving to another device will really break data, then this is a good time to fix the problem. Breaking things is allowed, look at modules. -- bill davidsen <davidsen@tmr.com> CTO, TMR Associates, Inc Doing interesting things with little computers since 1979. - 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 | |||||||||||||