[Bug 877] ssh 3.8.1p1 client cannot disable encryption with "-c none"

bugzilla-daemon at mindrot.org bugzilla-daemon at mindrot.org
Tue Jun 8 06:09:59 EST 2004


------- Additional Comments From jason at devrandom.org  2004-06-08 06:09 -------
> 10 Mbps networks hardly imposed any ovhd on the CPUs - my company is starting
> to use 1 Gbps networks - there the ovhd can be significant.

  The overhead also is dependant on how you've setup your GigE network.  Most
OSes and network devices are pretty configurable and you can really mitigate the
effects of the NIC overhead in your boxes.  GigE flow-control is also a must in
any higher-traffic GigE network.  I'm pushing 990mbps in testing with very low
CPU overhead on Linux through a variety of tuning practices.

  However the added bulk of encryption traffic on the network is going to be
negligible and realistically the encryption overhead in the CPU shouldn't be
that much of a resource starvation to your machines.  If it is, then you're in a
business-case ROI for upgrading or replacing H/W based on your needs.  Or
changing your usage on the boxes (i.e. use something unencrypted like telnet).

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

More information about the openssh-bugs mailing list