Hello,

I have been testing ssh240, ssh241, and ossh252p2 on Solaris
machines for performance.  As most people have probably found
out, secure shell is very slow.  We are leaning at using open secure
shell since it has faster transfer rates.  I was curious if anyone has
modified the open secure shell code to include a cipher of none.
I know this defeats the purpose of using secure shell but was
curious since it is an option on secure shell 240 and 241.

Thanks for any input.

Chuck Nelson
Sr. Sys. Eng.
CSG

Kevin O'Brien wrote:

> We've noticed the problem since 2.3 came out.  I've sent in a couple
> messages and no one seems to acknowledge it's existence.
>
> Kevin O'Brien
> Systems/Network Administrator
> E! Online, LLC
> 323.692.4742
> 323.692.4700 fax
>
> -----Original Message-----
> From: David Cress [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, April 24, 2001 11:43 AM
> To: SSH Mailing List
> Subject: OpenSSH v2.5.2p2 connection hanging on exit / Multiple OS's
>
> We just moved from SSH v1.2.27 to OpenSSH v2.5.2p2 on our systems, primarily
> Solaris 7.
>
> If I ssh to a system, start a job that forks off, and try and exit, my
> connection hangs, i.e.
>
>         atlcn291# /opt/ns/https-cnn/start
>         <iPlanet start messages>
>         atlcn291# exit
>
>         HANG
>
> This is very bad, we have scripts that do automated procedures, when they
> hang
> processing the first of over 200 machines, it causes us a bit of a problem.
> :)
>
> We also see this problem on our RedHat 6.2 machines.
>
> Interestingly enough, this only occurs with the C, and Korn shells, the
> Bourne
> shell does not hang.  I believe this is because the Bourne shell has no job
> control.
>
> We saw this problem in SSH v1.2.30, so moved back to v1.2.27, we really need
> to
> move to v2 of SSH, but .....
>
> Any help would be greatly appreciated.
>
> --
> David Cress
> Manager, System Administration Services
> CNN Internet Technologies
> http://www.cnn.com
> --------------------
> (404) 878-1921
>
> What exists, exists; what is, is.

Reply via email to