Delete cryptoloop
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
You wrote on linux.kernel:
Quoted 11 lines
Quoted 2 lines · [email protected] wrote:
Hopefully someone else will follow up, but I hope I'm somewhat convincing:
Not really ;)
Your points can be simplified to "I don't use cryptoloop, but someone else might" and "we shouldn't do this in a stable kernel".
Well, I want to hear from "someone else". If removing cryptoloop will irritate five people, well, sorry. If it's 5,000 people, well maybe not.
I use cryptoloop and I would be really annoyed if it disappeared in the stable kernel series. Besides, I read in another mail in this thread that dm-crypt will not work with file-based storage (I'm using cryptoloop on a file), and that it is new and potentially buggy.
I'm really surprised that people here argue that dm-crypt doesn't get enough testing so cryptoloop has to go to force people to test dm-crypt with their valuable data. This is all upside-down. First dm-crypt has to be stable, safe and feature-complete, then people can convert their data to dm-crypt and only then can cryptoloop be deleted.
Walter
Quoted 11 lines · Walter Hofmann
You wrote on linux.kernel:
Quoted 5 lines
Your points can be simplified to "I don't use cryptoloop, but someone else might" and "we shouldn't do this in a stable kernel".
Well, I want to hear from "someone else". If removing cryptoloop will irritate five people, well, sorry. If it's 5,000 people, well maybe not.
I use cryptoloop and I would be really annoyed if it disappeared in the stable kernel series. Besides, I read in another mail in this thread that dm-crypt will not work with file-based storage (I'm using cryptoloop on a file), and that it is new and potentially buggy.
Just to clarify this one point...
Device-Mapper (and thus dm-crypt) can only create mappings on block-devices. However, in your situation, you could just take a two-step approach of creating a loop device on the encrypted file (using losetup), and then using dm-crypt on top of this loop device.
Signature · 3 lines
Kevin Corry [email protected] http://evms.sourceforge.net/
Am Fr, den 23.07.2004 um 9:01 Uhr -0500 schrieb Kevin Corry:
Quoted 10 lines
Quoted 4 lines
I use cryptoloop and I would be really annoyed if it disappeared in the stable kernel series. Besides, I read in another mail in this thread that dm-crypt will not work with file-based storage (I'm using cryptoloop on a file), and that it is new and potentially buggy.
Just to clarify this one point...
Device-Mapper (and thus dm-crypt) can only create mappings on block-devices. However, in your situation, you could just take a two-step approach of creating a loop device on the encrypted file (using losetup), and then using dm-crypt on top of this loop device.
Yes, just look at the Wiki page on http://www.saout.de/misc/dm-crypt/ , people have contributed a lot of scripts.
Quoted 11 lines · Walter Hofmann
You wrote on linux.kernel:
Quoted 9 lines
Quoted 1 line · [email protected] wrote:
Hopefully someone else will follow up, but I hope I'm somewhat convincing:
Not really ;)
Your points can be simplified to "I don't use cryptoloop, but someone else might" and "we shouldn't do this in a stable kernel".
Quoted 8 lines
Quoted 2 lines
Well, I want to hear from "someone else". If removing cryptoloop will irritate five people, well, sorry. If it's 5,000 people, well maybe not.
I use cryptoloop and I would be really annoyed if it disappeared in
the stable kernel series. Besides, I read in another mail in this thread that dm-crypt will not work with file-based storage (I'm using cryptoloop on a file), and that it is new and potentially buggy.I'm really surprised that people here argue that dm-crypt doesn't get enough testing so cryptoloop has to go to force people to test dm-crypt with their valuable data. This is all upside-down. First dm-crypt has to be stable, safe and feature-complete, then people can convert their data to dm-crypt and only then can cryptoloop be deleted.
Not to mention working with mount... That would be good if we didn't have to train people, change scripts, etc.
Signature · 3 lines
-bill davidsen ([email protected]) "The secret to procrastination is to put things off until the last possible moment - but no longer" -me