SSH authentication bypass?

[Tom Buskey]

On Thu, Jun 26, 2014 at 3:00 PM, Kevin D. Clark <kevin_d_clark at comcast.net>
wrote:

>
> Mark Komarinski writes:
>
> > HPN SSH (patches to boost ssh performance) allows for no encryption
> > of the data stream but IIRC the authentication is encrypted.  That
> > doesn't bypass authentication so this may not be related
>
> The following statement is based on my experience with these patches:
> I didn't notice much of a difference from these patches when I was
> copying a certain {large-ish, constantly updating} file from a site on
> the West Coast to a site in NH.
>
>
There was a neat article in Linux Journal (?) that compared
compression/decompression time, bandwidth, data compressibility and cpu
speed.

At the end, there was a 3d graph that showed the results.  If you have
infinitely fast bandwidth, running compression is a waste.  If your CPU is
infinitely fast, compression takes no time and should always be done.  I
think you hit one of the areas where the speed of compression/decompression
at either end matched the reduction in bandwidth usage from compressing
your data.

For example, if your data is compressible enough and you have a
cpu/algorithm that is fast enough, you can effectively push more then 11.2
MB/s through 100mb ethernet.  If your data is not compressible, the time of
the compression will just slow things down.  Encryption usually includes
compression too.

There were a places on the graph where compression just increased the
bandwidth.  And places where the bandwidth made even 1% compression
significant.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.gnhlug.org/mailman/private/gnhlug-discuss/attachments/20140626/8bc2927c/attachment.html