[SLE] SLUG SuSE problem [fwd from pdbeal@louisville.edu]
Greetings, I've included a partial email that was sent to SuSE support. I also wanted to include it to the mail list to see if anyone else with similar needs has encountered similar problems. Please note that we are aware of problems that may occur when using RedHat rpms on non-RedHat systems. We thought it was worth a try on a test system ;-) We are surprised however at the lack of MD5 password capabilities in SuSE's options and sudo binaries. In addition we're surprised at the difficulty that we are having adding MD5 from compiled binaries on SuSE machines. Any ideas, experiences or success stories out there? ----- Forwarded message ----- Currently we have two major machines in the lab, both run linux and have syncronized /etc/passwd and /etc/shadow files. Both systems currently run Debian 2.2 with md5 passwords. Currently we are working to switch one system over back to SuSE. The switch was made due to md5 encryption needs. Originally the Systems both ran SuSE 6.0. I have been working with my copy of SuSE 6.4, to enable md5 passwords. I have modified /etc/pam.d/passwd to include md5 modules for passwords. With this change the system will encrypt md5 passwords. The problem arises with sudo. When a user who has sudo rights and has a shadow password, everything works fine. However, if a user has sudo rights and an md5 encrypted password, sudo doesn't verify the password. Sudo just returns "bad password" phrases. I have tried recompiling sudo to include md5 passwords from source, but the problem still remains. I have even gone as far as to use the sudo rpm from redhat, and also rebuilt the SuSE sudo.spm. When I use the redhat rpm, it complains of missing module or unknown module md5. Is there a way to use md5 passwords on SuSE and maintain the use of sudo? Sudo is the only package that hasn't worked on the test box with md5 passwords, but works flawlesly without md5 passwords. Is there a way to run md5 passwords and sudo without rebuilding all the pam modules my hand from source? We (Bill Sandman and I) have been talking and would like to know the reasons for not having the option to run md5 passwords. Most every distribution we know of runs either md5 passwords, or an option to run the md5 passwords, without hand editing files. I prefer to run SuSE over Debian, but it is vital that it must use md5 passwords and still have sudo working. And I can't install SuSE on one of our main machines without md5 passwords. ----- End forwarded message ----- Many thanks in advance for your ideas or observations. best, -- Wm. J. Sandman III Need Win95 or BETTER? Systems Programmer MacOs crashed your new G3? Internet Tool & Die Try Linux... wsandman@tool.net It's not just for breakfast anymore. PGP Key fingerprint = 7C C5 22 45 07 62 4C D9 94 CA C7 C1 44 FF BA D4 <HR> <UL> <LI>application/pgp-signature attachment: stored </UL> -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
participants (1)
-
wsandman@tool.net