Pete, the client is using ssh1 xyloci, but the server is ssh2! For this to work
the server needed to be built with ssh1 comatability and have a previous version
of sshd (sshd1) (1.2.26 or greater I believe) to work. The way SSH Secure Shell
2.x.x works with v1 clients is to fire up the sshd1 program and pass off the
connection.
First look on the server and make sure it has sshd1 installed. If it does then
you need to look in the sshd2_config file and make sure it is pointing to the
proper location for the version 1 daemon (sshd1). There are other options as
well, so look at man sshd2_config for more info.
If this still fails, then you may need to rebuild sshd2 (SSH Secure Shell
v2.4.0) on the server to let it know you have ssh v1 and you want to enable
handing off old client connections. If you don't have sshd1 installed, then the
server needs to get ssh v1.2.30 (I believe this is the latest, but get the
highest 1.2.x version on ftp.ssh.com--actually a mirror is better, they are
listed at ftp login) build it and then rebuild v2.4.0 and let it know you have a
previous v1.2.x installed.
I hope this helps.
--Dave
>Date: Fri, 16 Feb 2001 08:33:08 -0500 (EST)
>From: "Peter J. DiCostanzo Jr. - ComPath Inc." <[EMAIL PROTECTED]>
>X-Sender: [EMAIL PROTECTED]
>To: Mats Andersson <[EMAIL PROTECTED]>
>cc: [EMAIL PROTECTED]
>Subject: Re: daemon start banner?
>MIME-Version: 1.0
>
>This the output i get when trying to use ssh1 (yes compatability is set
>correctly)
># ssh1 xyloci
>Bad remote protocol version identification: 'sshd2: SSH Secure Shell 2.4.0
>(non-commercial version) on i586-pc-linux-gnu
>'
>
>Which seems to be a result of the extra line... not to mention that other
>people who have compiled it, do not have this line showing up.. which in
>itself is odd..
>-pete
>
>On Fri, 16 Feb 2001, Mats Andersson wrote:
>
>>
>> Hi,
>>
>> On Thu, 15 Feb 2001, Peter J. DiCostanzo Jr. - ComPath Inc. wrote:
>> > However, when I'm connecting, I am getting 2 lines of data.
>> ...
>> > sshd2: SSH Secure Shell 2.4.0 (non-commercial version) on
>> > i686-pc-linux-gnu
>> > SSH-1.99-2.4.0 SSH Secure Shell (non-commercial)
>>
>> This seems perfectly in order since the drafts for the protocol says that
>> there might be such lines before the one starting with "SSH-". Nothing
>> should break because of this and if it does it's broken and should be
>> fixed :-).
>>
>> Cheers,
>>
>> /Mats
>>
>>
>
--
David Knight French
Black Mountain Computer Consulting
Voice: (858)279-4862
Email: [EMAIL PROTECTED]
