On Tue, 27 Jun 2000, W. Scott Wilburn wrote:> We have Macintoshes running Fsecure SSH client 1.0.1 which are unable to > connect to a server running Openssh 2.1.1 on Red Hat 6.2. > > I believe that the problem is a bug with Fsecure, since a 30-day trial > version of 1.0.2 works fine. I'm a bit reluctant to tell all the Mac users > they have to spend money to upgrade, though, since everything was fine > until I switched my machines to OpenSSH from commercial SSH. > > Does anyone have any info on this? Is there a workaround?I think the version you are using is unable to connect to a server supporting the 2.0-protocol. Even if the server handles version-1.5. There is some problem in the initial handshake where the client gets confused by the version number it initially receives. The solution is to run the server in ssh-1.5 only mode. Or if you need 2.0-capability run a 1.5-server on another port. /MaF
Martin, Thanks. That is exactly what is happening. I found the readme for the latest Fsecure client and it says that bug is fixed. Unfortunately, simply telling the openssh server to only use ssh1 doesn't help with the old client. Scott On Wed, 28 Jun 2000, Martin Forssen wrote:> On Tue, 27 Jun 2000, W. Scott Wilburn wrote: > > We have Macintoshes running Fsecure SSH client 1.0.1 which are unable to > > connect to a server running Openssh 2.1.1 on Red Hat 6.2. > > > > I believe that the problem is a bug with Fsecure, since a 30-day trial > > version of 1.0.2 works fine. I'm a bit reluctant to tell all the Mac users > > they have to spend money to upgrade, though, since everything was fine > > until I switched my machines to OpenSSH from commercial SSH. > > > > Does anyone have any info on this? Is there a workaround? > > I think the version you are using is unable to connect to a server > supporting the 2.0-protocol. Even if the server handles version-1.5. There > is some problem in the initial handshake where the client gets confused by > the version number it initially receives. > > The solution is to run the server in ssh-1.5 only mode. Or if you need > 2.0-capability run a 1.5-server on another port. > > /MaF >-- *--------------------------------*-------------------------* | W. Scott Wilburn | Email: wilburn at lanl.gov | | Los Alamos National Laboratory | Phone: (505) 667-2107 | | MS H803 | Fax: (505) 665-4121 | | Los Alamos, NM 87545 | | *--------------------------------*-------------------------*
It does appear that F-Secure 1.0.1 on Mac does not like protocol versions
greater than 1.5. However, why does OpenSSH 2.1.1 (with ssh2 disabled)
advertise that it supports protocol version 1.99?
SSH-1.99-OpenSSH_2.1.1
On Wed, 28 Jun 2000, Martin Forssen wrote:
> On Tue, 27 Jun 2000, W. Scott Wilburn wrote:
> > We have Macintoshes running Fsecure SSH client 1.0.1 which are unable
to
> > connect to a server running Openssh 2.1.1 on Red Hat 6.2.
> >
> > I believe that the problem is a bug with Fsecure, since a 30-day trial
> > version of 1.0.2 works fine. I'm a bit reluctant to tell all the
Mac users
> > they have to spend money to upgrade, though, since everything was fine
> > until I switched my machines to OpenSSH from commercial SSH.
> >
> > Does anyone have any info on this? Is there a workaround?
>
> I think the version you are using is unable to connect to a server
> supporting the 2.0-protocol. Even if the server handles version-1.5. There
> is some problem in the initial handshake where the client gets confused by
> the version number it initially receives.
>
> The solution is to run the server in ssh-1.5 only mode. Or if you need
> 2.0-capability run a 1.5-server on another port.
>
> /MaF
>
--
Mike Fisk, RADIANT Team, Network Engineering Group, Los Alamos National Lab
See http://home.lanl.gov/mfisk/ for contact information