Hi, On Fri, Jan 07, 2005 at 04:05:23PM +0100, Max Vozeler wrote: > On Sat, Oct 30, 2004 at 05:12:37PM -0500, Manoj Srivastava wrote: > > It would be really nice if we could get this into util-linux, > > I agree, that would be great. OTOH we should aim to make the result > compatible for users of the existing crypto support, which is not > the case with the patch as-is. I've been looking into what changes > would be required. Here is what I have found so far: > > - The two patches default to different hash functions. The loop-AES > patch defaults to sha256/384/512 (depending on the keysize); The > current crypto defaults to rmd160. Most current users would need to > add -H rmd160 to losetup (or 'phash=rmd160' to mount options) to > continue using existing encrypted images.
what about introducing a config file, e.g. /etc/mount-crypro-default, that contains only the word crypto or loop-AES. Mount/losetup's default behavior is then the one or the other. (They could default to crypto if the conffile is absent.) Regards, Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
