Mr. Warner, et al.: I recently checked my Linux configuration, and noticed that I hadn't ticked off the experimental crypto box under the loop back device. Now I was able to use the losetup to do crypto. Why does everyone say its broken? Seems to have worked for me (using the 2.4.6 kernel + 2.4.6 kernel I-patch). Am I missing something here? Very Respectfully, Stuart Blake Tener, IT3, USNR-R, N3GWG 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. Sunday, July 08, 2001 7:23 PM -----Original Message----- From: owner-linux-crypto@xxxxxxxxxxxx [mailto:owner-linux-crypto@xxxxxxxxxxxx]On Behalf Of Adam Warner Sent: Sunday, July 08, 2001 2:52 AM To: linux-crypto@xxxxxxxxxxxx Subject: RE: Using Crypto under LM8+2.4.6 On 07 Jul 2001 19:57:09 -0700, IT3 Stuart B. Tener, USNR-R wrote: > Mr. Warner: > > I since turned on every menue option in the "menuconfig" relative to crypto > (mind you all in "M" or module selected mode), still the same problem. What > could I try next? Stuart, I've never had any problems (but I've never created modules either). This is the best kernel compile advice I can give: In Crypto options: Select Crypto support Select Crypto ciphers Select ciphers of choice Might as well also select the SHA-1 digest algorithm. In Block Devices (I suspect you missed this): Select Loopback device support Select Loopback encryption support If it still doesn't work then I'm lost for advice. > I am sorry, I must have been unclear in order to solicit the response you > sent. What I was referring to was integrating the crypto package into the > passwd program. Currently password stored in /etc/passwd are stored using > Unix cryptographic methods. I would rather use AES for example to encrypt > the passwords (login passwords, I mean) in the /etc/passwd. What I meant was > to leverage strong encryption where weak encryption is used right now to > encrypt password (as is done normally) in the /etc/passwd file. My understanding is MD5 password hashes can already be used. That's pretty strong. Plus with shadow passwords even the encrypted passwords aren't displayed in /etc/passwd (just an "x"). In other words there is no longer any problem to solve nor any encryption necessary in /etc/passwd. /etc/shadow can only be read by root. I'm not sure how long it would take to crack an MD5 password but it wouldn't be pretty. But you'd need root privileges to even see them! Regards, Adam 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/
