![]() | |||||||||||||
Messages in this thread |
On Fri, Jun 20, 2003 at 11:14:14AM -0700, David S. Miller wrote: > On Fri, 2003-06-20 at 10:56, Andrew Morton wrote: > > Andi Kleen <ak@suse.de> wrote: > > > > > > > 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. > > > > I think we should just live with that breakage Andi. You're suggesting > > that we retain compatibility with something which was never merged into the > > kernel. That is asking too much. > > There was effectively no cryptoloop support in the vanilla > kernel. Andi is totally right here. We should be compatible > with what people actually used, which were the external cryptoloop > patches. > > Nobody, and I mean nobody, has a cryptoloop based upon the IV > selection done in vanilla kernels. Ha David - you repeat what Clemens was saying and Andi disputed. Andries [I watch what is happening with interest - have delayed util-linux 2.12 in the hope of being able to come with something that works out of the box together with a sufficiently recent kernel. A handful of loop patches are needed. I hope they will be applied and documented one by one.] - 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 | |||||||||||||