OK Problem fixed. It's 2.9 going to 2.3 I needed to create the proper authorized_keys2 with proper permissions on the server AND I needed to recreate proper ./id_dsa.pub and ./id_rsa.pub files on the the client and include them, especially the DSA, into the server authorized_keys2. Of course, all fo this is well documented. I needed to walk through Dejanews to put all the peices together. That's why sysadmins get the big bucks... Now the problem is that SUSe doesn't have a openssh 3.0 RPM The source RPM on openssh.org's sites seems, to my eyes, to be asking for Redhat specific RPM dependencies. Should I just roll my own with openssl and openssh? Ruben On 2002.01.25 17:33:49 -0500 Michael Osten wrote:

...

Are you using 2.9x on one machine and 3.0.x on the other?

--------- ------------- Michael Osten Reefedge Inc.

--

Brooklyn Linux Solutions __________________________ http://www.mrbrklyn.com - Consulting http://www.brooklynonline.com - For the love of Brooklyn http://www.nylxs.com - Leadership Development in Free Software http://www.nyfairuse.org - The foundation of Democracy http://www2.mrbrklyn.com/resources - Unpublished Archive or stories and articles from around the net http://www2.mrbrklyn.com/mp3/hooked.mp3 - Spring is coming.... http://www2.mrbrklyn.com/downtown.html - See the New Downtown Brooklyn.... 1-718-382-5752