From: Alexander Nyberg <alexn@dsv.su.se>
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org
Subject: dm-crypt vs. cryptoloop reminder
Date: Sat, 05 Mar 2005 22:35:24 +0100 [thread overview]
Message-ID: <1110058524.13821.17.camel@boxen> (raw)
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@kroah.com>
+
+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/
next reply other threads:[~2005-03-05 21:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-05 21:35 Alexander Nyberg [this message]
2005-03-05 22:44 ` dm-crypt vs. cryptoloop reminder Andries Brouwer
2005-03-09 19:32 ` Pavel Machek
2005-03-10 21:02 ` Matt Mackall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1110058524.13821.17.camel@boxen \
--to=alexn@dsv.su.se \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox