We saw this, either with, I think with for the Mac. The exchange of
version information didn't work, so the server never fell back to
ssh1. Our (temporary) workaround was to put an ssh1 server up on
another port and have the Macs use it.
(we saw this with ssh2 ... haven't tried it with openssh)
Dave Brent, UBC Computer Science
On Tue, 27 Jun 2000, W. Scott Wilburn wrote:
> Date: Tue, 27 Jun 2000 16:09:43 -0600 (MDT)
> From: W. Scott Wilburn <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: F-secure -> Openssh Compatibility
>
>
> 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?
>
> Symptoms
> --------
>
> Client side (Mac w/ Fsecure):
>
> After initiating connection, nothing happens until eventual timeout or
> manual quit.
>
> Server side (Linux w/ Openssh)
>
> Log file reads
>
> Connection from <client IP> port 49153
>
> After client-side quit, log file reads
>
> Did not receive ident string from <client IP>.
>
>
> Best regards,
> Scott Wilburn
>
> --
> *--------------------------------*-------------------------*
> | W. Scott Wilburn | Email: [EMAIL PROTECTED] |
> | Los Alamos National Laboratory | Phone: (505) 667-2107 |
> | MS H803 | Fax: (505) 665-4121 |
> | Los Alamos, NM 87545 | |
> *--------------------------------*-------------------------*
>
