Hi Gareth, I found that compression doesn't work from neither
MacOS X / Darwin ( OpenSSH_3.1p1, SSH protocols 1.5/2.0 ) nor FreeBSD 4.4 ( SSH Version OpenSSH_2.3.0 FreeBSD localisations 20010713, protocol versions 1.5/2.0. ) nor Linux (SSH Version OpenSSH_2.3.0p1, protocol versions 1.5/2.0. Compiled with SSL (0x0090600f).) so whenever you try and start it with the -C option ( for compression ) the cobalt answers with compression refused. Perhaps you have turned on compression somewhere and MacSSH can't handle that reply. I'm not familiar with MacSSH but I recommend you have a look in the config file. Cheers - Gerrit Am Freitag den, 28. Juni 2002, um 09:56, schrieb Gareth Watkins: > Has anyone had issues connecting using SSH2 after a successful upgrade > to > OpenSSH 3.4p1 on a RAQ3. > > My client is MacSSH on Macintosh. > > I saw someone mention that there was a " certain compression protocol > in > the new version has been broken, the solution was to force blowfish or > 3des > instead. " > > My question is "instead" of which protocol - what is the default > protocol as > I don't see an option for this in MacSSH ..? > > Would this be due to the compression issue ? Do I get another client? > > thanks in advance > Gareth > > _______________________________________________ > cobalt-developers mailing list > [EMAIL PROTECTED] > http://list.cobalt.com/mailman/listinfo/cobalt-developers > > ======================================================== Fingerprint: 867B FA79 B7F6 A004 8303 A97B AE75 E599 AE9E BD75 ======================================================== _______________________________________________ cobalt-developers mailing list [EMAIL PROTECTED] http://list.cobalt.com/mailman/listinfo/cobalt-developers
