-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2007-02-11 at 02:06 +0100, I wrote:
I have bumped into a weird problem with encrypted filesystems.
It appears there are two incompatible types that use the same options in the cryptotab file.
It's difficult to explain.
Let me explain in another way: Encrypted filesystems using 'twofish256', created after mounting another filesystem that uses 'twofishSL92', are in fact created using 'twofishSL92' as well, silently. Thus, the keyword 'twofish256' refers in fact to two different and incompatible encryptions: to the real or new 'twofish256' (reported by losetup as 'CryptoAPI/twofish-cbc'), and to the old 'twofishSL92' (reported by losetup as 'twofish256'). The proof of this is that I can happily mount my 'twofish256' filesystems as 'twofishSL92' instead. Now, the first question is: is there another token I can use instead of 'twofish256' that is unique and refers to the real 'twofish256', that is, to 'CryptoAPI/twofish-cbc'? And the other question (to SuSE developers) is, how long will the 'twofishSL92' be maintained? (I have dozens of dvd backups made using 'twofish256' that are in fact 'twofishSL92') - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFzviStTMYHG2NR9URAsB4AJ4iW7+ILw/cX8deULn2EGPa12VjgwCcCHB2 Sa/wUgWJAsAsyakkbm3a74E= =aBQP -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-security+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-security+help@opensuse.org