Dear Sir or Ma'am: I have several suggestions to make, and I hope they help with your issues. I had severe trouble trying to make the 2.4.3.1 patch work with my RH installation (or Mandrake, an RH derivative). First of all I have been a supporter of RedHat for the longest time, due mostly in part to IBM's support of RedHat, and it has been a supported distribution from most of the major software vendors (Oracle, Informix, etc.). However, recently I downloaded Linux-Mandrake 8.0, and have been extremely pleasantly surprised. It is a very "GUIized" Linux, and is very easy to administer and manage. If you like RedHat, this is RedHat on steroids. I initially switched as I wanted to try the ReiserFS JFS, and then I liked the OS in general. Even though most likely at this juncture I am eventually going to run ext3 as my JFS, I still am planning to stick with Mandrake once I verify that the Oracle install I am going try will work. Even though I hate the idea, I switched from the distributions kernel to a standard "Linus" kernel from kernel.org, and further moved to 2.4.6 which has been working quite well. Once I did this, I was able to install and use the 2.4.6 I-patch (International Patch), which as I am sure you are now aware from reading the list is the subject of a hot debate as to its future and how it will be repaired and reworked to be made better. Eventually, after making sure I had all the right options "ticked" off in the "make xmenuconfig" screens, I was able to use crypto. I am now worried about its stability until some further patches come out as a result of the blocking factor issues, but once the patches stabilize in the next week or two, I intend to run it full boat. Another option is the loop-AES software, which, while I am not using at the moment, since I do not NEED crypto right now, I will wait for the patch. But I am sure Mr. Ruusu will contact you off list to tell you about it, since he is its author. Very Respectfully, Stuart Blake Tener, IT3, USNR-R, N3GWG Beverly Hills, California VTU 1904G (Volunteer Training Unit) stuart@xxxxxxxxxxx west coast: (310)-358-0202 P.O. Box 16043, Beverly Hills, CA 90209-2043 east coast: (215)-338-6005 P.O. Box 45859, Philadelphia, PA 19149-5859 Telecopier: (419)-715-6073 fax to email gateway via www.efax.com (it's free!) JOIN THE US NAVY RESERVE, SERVE YOUR COUNTRY, AND BENEFIT FROM IT ALL. Wednesday, July 11, 2001 1:05 AM -----Original Message----- From: owner-linux-crypto@xxxxxxxxxxxx [mailto:owner-linux-crypto@xxxxxxxxxxxx] On Behalf Of Tuukka Toivonen Sent: Wednesday, July 11, 2001 12:59 AM To: linux-crypto@xxxxxxxxxxxx Subject: problems with crypto and 2.4.3 I patched my 2.4.0 kernel up to 2.4.3 and applied -rw-r--r-- 1 root ftp 274007 Jul 6 18:34 patch-int-2.4.3.1.bz2 this patch. Everything seemed to be ok after compiling and installing the new kernel. Then I downloaded -rw-r--r-- 1 tuukkat tuukkat 1299742 Jul 11 10:41 util-linux-2.11b.tar.gz and applied -rw-r--r-- 1 root root 46208 Jul 6 18:41 util-linux-2.11b.patch and compilation went fine. Copied binaries in their places, but I get [root@xxxxxxxxxx /]# losetup -e blowfish /dev/loop0 /.crypto Available keysizes (bits): 128 160 192 256 Keysize: 160 Password : Password : The cipher does not exist, or a cipher module needs to be loaded into the kernel ioctl: LOOP_SET_STATUS: Invalid argument [root@xxxxxxxxxx /]# cat /proc/modules loop 8576 0 (autoclean) parport_pc 14192 1 (autoclean) lp 5360 0 (autoclean) (unused) parport 15936 1 (autoclean) [parport_pc lp] cipher-blowfish 9344 0 (unused) cryptoapi 2784 2 [cipher-blowfish] nls_iso8859-1 2864 22 (autoclean) ... I also tried other ciphers with same results. This is redhat 6.2 and libc-2.1.3.so. AMD Athlon 800 MHz, 256 MB main memory. I'm using devfs (if that matters). Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/ Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
