Mr. Ruusu, et al.: I understand that loop-aes and cryptoloop are stacking device technologies; however, I am also trying to ferment a plan to implement everything cohesively. Fair enough, I am game. I am going to try to devise a method to make use of loop-aes, EVMS, and ReiserFS without the need for suggesting that a new "code bureaucracy" be created for EVMS. Although I do know that already the plan (from IBM) is to have such plug-ins, I do not think people on the EVMS team have the experience with encryption to write such code. That being said, I would presume that the first layer should be loop-aes, then EVMS, then ReiserFS; and that my /boot partition would need to be an unencrypted, and outside the control of EVMS. I am also wondering if there would be a problem keeping ReiserFS and EVMS as modules within the initrd also? Does this sound plausible? Since one person told me that, the issue I have had with using DEVFS is related to initrd usage over ReiserFS (I plan to test this later this week) I am willing to forgo the need for DEVFS for the moment, since it would be a convenience at best right now. However, eventually it would be my desire to also include the use DEVFS into the mix. One other thought is if loop-aes technology were a plug-in for EVMS would that not make having encrypted swap a much more simple process? Very Respectfully, Stuart Blake Tener, IT3 (E-4), USNR-R, N3GWG Beverly Hills, California VTU 1904G (Volunteer Training Unit) stuart@bh90210.net 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. Monday, April 01, 2002 1:56 AM - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
