Slow connection performance with ssh2

[mouring at etoh.eviladmin.org]

If one read the SSH v2 specs they would realize more crypto work is being
done in v2 upfront using D/H.  Markus and others did improved it.  A SS20
150mhz box connects at about 25 seconds.  But when compared to my dual
533mhz it is slow (which is almost instant).

I have a U10 over here which I'll be testing sometime this month, but
there is not much one can do.  Even v2 on NeXT Black slab (68k-25mhz)  is
slow.

It would be intersting to benchmark SSH Corp and vshell on slow boxes to
see where we stand, but I suspect they will be the same or we will be
slightly faster. (We do have the best crypto people in OpenBSD, right
Theo? =)

- Ben


On Sun, 4 Nov 2001, Gert Doering wrote:

> Hi,
>
> On Sun, Nov 04, 2001 at 09:05:19AM -0500, Gregory Leblanc wrote:
> > > As my hardware is slower (Sparc LX, NetBSD, 50 MHz CPU) it takes more
> > > than 2 minutes (!!), which are spent on CPU cycles in ssh and sshd - running
> > > with 95% CPU... - the overall CPU time used by sshd for a successful
> > > connect is about 2:50 minutes
> >
> > Older SPARCs in general are bloody slow at encryption operations.
>
> I know that :-) (still: ssh protocol 1 connects in less than 5 seconds).
>
> > Try upgrading to 2.9.9p2, and make sure that you're -not- using DSA, as
> > that's REALLY REALLY slow.
>
> I did disable DSA already (I removed the DSA host key (and restarted
> sshd), which should be sufficient, no?).  Will try 2.9.9p2...
>
> gert
> --
> USENET is *not* the non-clickable part of WWW!
>                                                            //www.muc.de/~gert/
> Gert Doering - Munich, Germany                             gert at greenie.muc.de
> fax: +49-89-35655025                        gert.doering at physik.tu-muenchen.de
>