Milan Broz wrote: > On 06/14/2012 01:47 PM, Ludwig Nussel wrote: >> Karel Zak wrote: > >> Well, someone could come up with another tool to support cryptoloop, or >> rather 'transfer functions'. > > cryptsetup can map all compatible mappings with cryptoloop using dmcrypt > (and it can automatically alloc loop device as well) so providing something > compatible is just question of simple wrapper. > > IMHO cryptoloop should be removed from kernel... The only usable (and secure) > solution using this interface is out-of-mainline-tree loop-aes extension. Sure. Who is going to send the patch? I don't think this needs to be the precondition to remove the incomplete encryption support from losetup. On the contrary, the current losetup support makes cryptoloop even worse as there's no support for hashing the passphrase nor a way to e.g. pipe a random key into losetup. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) -- To unsubscribe from this list: send the line "unsubscribe util-linux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
