-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I am a little confused about cryptoapi implementation on kernel 2.4.21 and 2.4.22. I can see a new submenu named 'Cryptographic options' wich contains various digest algorithms, aes and other. Does anyone can explain me what is happening? The patch-int from ftp://ftp.kernel.org/pub/linux/kernel/people/hvr/testing will no longer be required? Does the current kernel version contain a stable (and usable) implementation of cipher algorithm like aes, twofish, blowfish and serpent ? New kernel versions will ship with a full implemention of cryptoapi and will not need patch? Actually I'm running a 2.4.20 with patch-int-2.4.20-1, and I have about 120gb of encrypted data with aes-twofish since a year ago. I had some problems applying the patch-int-2.4.21.0 to the kernel 2.4.21. but now with 2.4.22 and patch-cryptoloop-hvr-2.4.22.0 I can see that the cryptoloop support is now located under block devices and all seems ok. Does anyone can tell me if I can upgrade to kernel 2.4.22 with the last cryptoloop-hvr patch without losing my data and if the new cryptographic api is backward compatible with my 2.4.19? Thank you - -- Alessandro Avagliano - GnuPG keyid 2460969F [Key fingerprint: 41BB B286 82DD 6D74 EF43 9CF3 AC03 9586 2460 969F] Random signature follows: -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/TAjcrAOVhiRglp8RAqU/AKCIA8UwFp+zJCTnw6Z0Wk7Jv1/4hgCdEPyd E6H23VKNpqXuXG+2yBM4CBk= =Qj5s -----END PGP SIGNATURE----- - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
