That sounds like openssh-3.4p1-77 is defaulting to Protocol 2 only. My security people made me make that switch. Now I secify DSA when I do a keygen and put the public keys in authorized_keys2.
/Thomas Kern /301-903-2211 > -----Original Message----- > From: Wolfe, Gordon W [mailto:[EMAIL PROTECTED] > Sent: Monday, August 04, 2003 16:01 > To: [EMAIL PROTECTED] > Subject: ssh connect no password > > > As part of my remote maintenance system for managing many > linux images under VM (See my talk at SHARE in DC, Session > 9343) I make heavy use of ssh. In order not to have to > provide a password each time I update a file or run a > command, I've been using ssh's trusted-server authentication > method with public and private keys. Unfortunately, since > going to SLES8, I haven't been able to get it to work. > > Under SLES7, I used openssh-2.9.9p2-67. to allow file > transfers and command usage without passwords, I just did the > following: > > (1) copied the remote file /etc/ssh/ssh_host_key.pub and > appended it to the local file /etc/ssh/ssh_known_hosts and also to > /root/.ssh/known_hosts > > (2) did ssh-keygen from root. > > (3) copied the local file /root/.ssh/identity.pub to the > remote file /root/.ssh/authorized_keys. > > That's it! > > Now on SLES8, with openssh-3.4p1-77, this process doesn't > work any more. ssh works, but it requires me to manually > input the password each time. For one thing, ssh_keygen > requires me to specify if it's dsa or rsa. Also, there's a > second package there, openssh-askpass-3.4p1-61. > > Any ideas what I'm missing? > > "Great Minds discuss ideas. Average minds discuss events. > Small minds discuss people." - Admiral Hyman Rickover > Gordon Wolfe, Ph.D. (425)865-5940 > VM Enterprise Servers, The Boeing Company >
