The reason for this is simple, tho I've asked in this mailing list, irc,
various web boards... Everyone says this is the way it should be... in
the PRE 2.4.0 days ... when you connect to port 22 of a box running ssh in
inetd mode OR standalone mode.. you would receive the following output:
SSH-1.99-2.4.0 SSH Secure Shell (non-commercial)
except with correct version numbers of course... NOW if you telnet
localhost 22, you will see the following:
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)
TWO lines of output.. ssh version one is expecting the second line only,
which identifies version number... ever since i have installed ssh version
2 .. and specified ssh1 compatability (at compile time) AND in the conf
file no ssh1 clients have been able to connect.. =(
However, the few people that have responded insisted that this is
correct according to the notes on the new protocol. This doesnt make
sense to me because this makes it non-backward compatable.. Anywhoo try
it out....
I realize this isn't a solution.. but at least you know what the problem
is.
-pete
--
''~``
( o o )
+-------------------------.oooO--(_)--Oooo.-----------+
| Peter J. DiCostanzo Jr. ComPath Incorporated |
| Systems Engineer -= www.compath.com =- |
| (Solaris / Linux / NT) [EMAIL PROTECTED] |
| [EMAIL PROTECTED] |
| |
|Disk space is too good .oooO |
| for them -BOFH #11 ( ) Oooo. GOT LINUX?|
+----------------------------\ (----( )-------------+
_) ) /
(_/
On Tue, 6 Mar 2001, Ravindra Chimata wrote:
>
>
>
> Platform : HPUX 10.20 with trusted mode
> ssh-2.4.0 from ssh communications security
> ssh-1.2.31 from ssh communications security
> gcc compiler.
>
> I compiled ssh1 first on HPUX 10.20 using gcc successfully and then compiled
> ssh2 on the same server. The following changes were made in
> /etc/ssh2/sshd2_config to allow ssh1 compatability ( Ssh1compatability=yes,
> Ssh1Path=/opt/ssh/sbin/sshd1 ).
>
> Now if I run sshd ( sshd2) using -i option in inetd mode ( sshd -i ), I am able
> to connect successfully using ssh2 client. If I try to conenct using ssh1 client
> , the connection is unsuccessfull with error "Bad remote protocol version
> identification".
>
> If I run sshd (sshd2) without -i option, I can connect using ssh2 & ssh1
> clients.
>
> Any suggetions or help is appreciated.
>
> Thanks,
> Ravindra
> [EMAIL PROTECTED]
>
>
Re: ssh2 & ssh1 compatability problem in inetd mode.
Peter J. DiCostanzo Jr. - ComPath Inc. Sun, 11 Mar 2001 09:51:04 -0800
- ssh2 & ssh1 compatability probl... Ravindra Chimata
- Re: ssh2 & ssh1 compatabil... Peter J. DiCostanzo Jr. - ComPath Inc.
- Re: ssh2 & ssh1 compatabil... Ravindra Chimata
