>> 	.	ssh cannot be configured to provide a channel without
>> 		high encryption overhead, which is undesirable.
>
>This is true only if you insist on using an implementation that refuses
>to support "none" encryption.

even if you were to use "none", you'd still suffer from the "framing"
and checksumming that ssh uses.  rsh, on the other hand, uses no
framing, so it can go faster.

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
werdna@squooshy.com       * "information is power -- share the wealth."