Skip to contentSkip to conversation

dm-crypt vs. cryptoloop reminder

PATCH Alexander Nyberg 4 participants 4 messages Mar 5, 2005 – Mar 10, 2005 Documentation

lore
Share & tools
lore
#0 lore 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 =====

Documentation/feature-removal-schedule.txt +7 -0
@@ -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 <[email protected]>
 
+
+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/
#1 lore raw
Quoted 3 lines · 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

Are you a troll?

This is not something to be quoted by anybody serious.

Andrew referred to "well-known weaknesses" in cryptoloop, and when I inquired it turned out that what he referred to were properties of cryptoloop and dm-crypt alike, so that his remarks that started that discussion were misguided.

Of course people may prefer dm-crypt or cryptoloop or loop-aes, just like people prefer ide-cd or ide-scsi.

I have not yet seen a valid reason to deprecate one of these three very soon.

Andries

#2 lore raw

Hi!

Quoted 13 lines
Quoted 3 lines

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

Are you a troll?

This is not something to be quoted by anybody serious.

Andrew referred to "well-known weaknesses" in cryptoloop, and when I inquired it turned out that what he referred to were properties of cryptoloop and dm-crypt alike, so that his remarks that started that discussion were misguided.

Quoted 5 lines

Of course people may prefer dm-crypt or cryptoloop or loop-aes, just like people prefer ide-cd or ide-scsi.

I have not yet seen a valid reason to deprecate one of these three very soon.

I'd say that "no-maintainer" + "maintained code can do the same" is enough, but... I thought that ide-scsi was deprecated, too?

Signature · 1 line
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms         
#3 lore raw
Quoted 15 lines · Pavel Machek

Hi!

Quoted 13 lines
Quoted 3 lines

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

Are you a troll?

This is not something to be quoted by anybody serious.

Andrew referred to "well-known weaknesses" in cryptoloop, and when I inquired it turned out that what he referred to were properties of cryptoloop and dm-crypt alike, so that his remarks that started that discussion were misguided.

Quoted 8 lines
Quoted 5 lines

Of course people may prefer dm-crypt or cryptoloop or loop-aes, just like people prefer ide-cd or ide-scsi.

I have not yet seen a valid reason to deprecate one of these three very soon.

I'd say that "no-maintainer" + "maintained code can do the same" is enough, but... I thought that ide-scsi was deprecated, too?

You can attach a file to loopback and then run dm-crypt on top of that, so I think it's completely duplicate functionality at this point.

Signature · 1 line
Mathematics is the supreme nostalgia of our time.