Sometimes this isn't possible - I couldn't figure out how to do that
with CVS, because "setenv CVS_RSH ssh" is required, and doing
"setenv CVS_RSH 'ssh -c blowfish'" doesn't work. The solution I've
implemented is to add the following lines to /etc/ssh_config :
Host *
Protocol 1,2
That makes it try protocol 1 first, then 2. Protocol 1 seems more solid
under the ssh client in 10.0.4. And since the directives are in the
global config file, it will fix it in all such situations. There may be
situations in which that's not desired, but it's worked well for me.
[EMAIL PROTECTED] (Ian Ragsdale) wrote:
>There is a problem with the ssh client that came with 10.0.4. The problem
>is only with the default cipher. To work around this, add a '-c blowfish'
>to the command line. This will use the blowfish cipher instead, and you
>should connect fine.
>
>Ian
>
>On 7/13/01 12:43 AM, "skazat" <[EMAIL PROTECTED]> wrote:
>
>> hey
>>
>> slight OT,
>>
>> but I'm trying to ssh into a sourceforge account using the terminal app and
>> ssh, I keep getting this back:
>>
>> Bad packet length 235817961.
>>
>> wassa?
>>
>> it's a perl project, so i feel justified to ask the q here
>>
>
>
------------------- -------------------
Ken Williams Last Bastion of Euclidity
[EMAIL PROTECTED] The Math Forum
