dm-crypt vs. cryptoloop reminder

[Alexander Nyberg]

2.6.3-mm1 'dm-crypt vs. cryptoloop' discussion was some time ago, it is
time to bring this up again:
http://kerneltrap.org/node/2433

I'm no cryptanalyst, but googling a bit shows a bunch of problems with
it (also see above thread), there is no maintainer and most importantly
there is a replacement for it that has active maintainers. Redundant
security solutions is a risky thing to me.



===== Documentation/feature-removal-schedule.txt 1.4 vs edited =====
--- 1.4/Documentation/feature-removal-schedule.txt	2005-01-14 22:22:44 +01:00
+++ edited/Documentation/feature-removal-schedule.txt	2005-03-05 22:13:12 +01:00
@@ -15,3 +15,10 @@ Why:	It has been unmaintained for a numb
 	against the LSB, and can be replaced by using udev.
 Who:	Greg Kroah-Hartman <greg@xxxxxxxxx>
 
+
+What:	cryptoloop
+When:	July 2005
+Files:	drivers/block/cryptoloop.c and parts of drivers/block/loop.c
+Why:	Unmaintained, has vulnerabilities that haven't been fixed.
+	Superseded by dm-crypt that has been in mainline for a long time 
+	now: http://www.saout.de/misc/dm-crypt/


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/