On Mon, 27 Dec 1999, George Dimitoglou wrote:

GD>     mv -f /usr/local/bin/ssh /usr/local/bin/ssh.old
GD>     mv: cannot access /usr/local/bin/ssh
GD>     *** Error code 2 (ignored)

the SSH install tries to move the old binaries out of the way.  if there
are no old binaries, you get the above errors.  nothing to worry about
here.

GD> Then, when I start sshd, and I try to ssh to another system that has SSH running, 
I get the following:

just so we all know, it's SSH2 on "system".

GD>     debug: client_disconnect: Illegal protocol version.

what is the remote side running?  telnet to port 22 on the other system to
find out.

GD> When I try to ssh TO the system I put SSH on, I get:
GD>     george@<system> ssh -v A -l george
GD>     SSH Version 1.2.26 [alpha-dec-osf4.0], protocol version 1.5.
GD>     Standard version.  Does not use RSAREF.
GD>     sohops.gsfc.nasa.gov: Reading configuration data /etc/ssh_config
GD>     sohops.gsfc.nasa.gov: ssh_connect: getuid 1042 geteuid 0 anon 0
GD>     sohops.gsfc.nasa.gov: Connecting to cdaw [xxx.xxx.xxx.176] port 22.
GD>     sohops.gsfc.nasa.gov: Allocated local port 1023.
GD>     sohops.gsfc.nasa.gov: Connection established.
GD>     sohops.gsfc.nasa.gov: Remote protocol version 2.0, remote software version 
2.0.13 (non-commercial)
GD>     sohops.gsfc.nasa.gov: Waiting for server public key.
GD>     Connection closed by remote host.

you're trying to use SSH1 to login to a SSH2 server, which I don't think
is allowed using a standard config (I don't use SSH2, so I could be wrong
on this.)  I seem to remember something about a ssh1 compatibility mode
that needs to be set.

-- 
Randomly Generated Tagline:
LILO, you've got me on my knees!
 (from David Black, [EMAIL PROTECTED], with apologies to Derek and the
 Dominos, and Werner Almsberger)

Reply via email to