Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Secure-Shell
[Top] [All Lists]

Hardware accelerators and RAM/CPU guidance

Subject: Hardware accelerators and RAM/CPU guidance
Date: Thu, 1 Jun 2006 10:01:55 -0600
I am seeking some advice on hardware for a dedicated SSH box.  I can't
seem to find any performance statistics for anything but SCP/SFTP
transfers and the HPN patches for fat pipes.

The goal is to support 500-1000 simultaneous SSH sessions, which are in
TCP port forwarding mode only.  The data travelling through the tunnel
will be small (about 1KB over the course of one minute).

The first question is whether crypto accelerator cards are actually
useful with this type of scenario (on the server)?  I looked at the
OpenSSH code and it seems that it only uses crypto accelerator cards for
specific tasks (keys on a smartcard).  The only calls that I see to the
OpenSSL functions that provide hardware acceleration (ENGINE_set_*) are
in "scard.c" and "scard-opensc.c" files.  So OpenSSH effectively doesn't
use any hardware accelerators supported by OpenSSL?  Is this correct?

The second question is how much RAM/CPU would be necessary to support
500-1000 simultaneous connections (assuming no hardware accelerator
support)?  This will probably be AMD64 CPUs.  Anybody have some
statistics or guidance they can share?

<Prev in Thread] Current Thread [Next in Thread>