Messages in this thread | | | From | Kevin Corry <> | Subject | Re: [PATCH] Delete cryptoloop | Date | Fri, 23 Jul 2004 09:01:33 -0500 |
| |
On Friday 23 July 2004 7:34 am, Walter Hofmann wrote: > You wrote on linux.kernel: > > 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.
-- Kevin Corry kevcorry@us.ibm.com http://evms.sourceforge.net/ - 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/
| |