ends up that it's because the newer versions of ssh-client try to connect
using version 2 of the protocol. i had a breeze through the config files,
and it looks like you should be able to get it to use protocols in a
particular order ie. try SSH1 first, then SSH2 but it ignores it. I haven't
managed to get ssh2 keys etc setup properly on the server.
To get around it, force the client to use ssh1:
ssh foo.fooplace.com -1
This doesn't work with scp, however.
Cheers,
Chris
-----Original Message-----
From: Hans Loehr [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 6 June 2001 07:46
To: Chris Herrmann
Cc: 'list'
Subject: Re: ssh 2.9 problems
Hi,
On Wed, May 23, 2001 at 03:46:09PM +1000, Chris Herrmann wrote:
> The ssh client gets "bad password".
>
> Now, assuming that I can remember the password... what could be going on
> here? If i ssh from another box the same error pops up. The debug output
Did you configure ssh to use MD5-passwords?
(I once had problems to install ssh on a redhat box; I had to set the
configure options manually before compilation
[ IIRC: --with-md5-passwords ])
> Chris
bye,
Hans
--
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* Hans Loehr * [EMAIL PROTECTED] *
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
