Messages in this thread | | | Subject | Re: dm-crypt using kthread (was: Oopsing cryptoapi (or loop device?) on 2.6.*) | From | Christophe Saout <> | Date | Mon, 16 Feb 2004 03:58:17 +0100 |
| |
Am Mo, den 16.02.2004 schrieb Andrew Morton um 02:53:
> > + This device-mapper target allows you to create a device that > > + transparently encrypts the data on it. You'll need to activate > > + the required ciphers in the cryptoapi configuration in order to > > + be able to use it. > > Is there more documentation that this? I'd imagine a lot of crypto-loop > users wouldn't have a clue how to get started on dm-crypt, especially if > they have not used device mapper before.
Yes, there is. I'm going to collect it and put something together.
> And how do they migrate existing encrypted filesytems?
The current on-disk-layout is compatible with cryptoloop. The IV generation mechanism is flexible though and will be extended to allow for a more secure IV generation (like using a hash algorithm).
At the moment it supports no IC (ECB mode) or plain IV (sector number truncated to 32 bit as IV).
- 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/
| |