Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a very slow connection, and I need to use SSH on it. How can I increase "the speed"? I mean is using big RSA keypairs a large overhead? Would lowering the key size increase the effective bandwidth a little?

share|improve this question
You claim this SSH connection is slow, but have you compared it to a Telnet connection between the same two hosts? Test with a locked-down dummy account if you think there's a real chance of password interception even for this one test; delete the account after the test is complete. Symmetric encryption overhead is typically swamped by network I/O overhead. For the reverse to be true, either the CPU has to be underpowered (or similar, e.g. oversubscribed VM) or you have to be on a very fast network. – Warren Young Jan 9 '12 at 9:04
ssh -X needed :\ – LanceBaynes Jan 9 '12 at 9:18
The problem with X is that it is a protocol which doesn't support very well high latency -- and applications are even worse that needed by the protocol in such context. You may want to use an X protocol compressors (I've never done that, I remember seeing some). Or switch to something like VNC. – AProgrammer Jan 9 '12 at 14:13
I recommend trying with -c blowfish -C. – Thorbjørn Ravn Andersen Jan 9 '12 at 14:50
up vote 7 down vote accepted

The RSA key size only matters at the time when the connection is established. The key size can matter if one of the machines is slow, as larger keys mean longer computations, but its impact on connection times is negligible.

If throughput is a problem, compress the connection: ssh -C.

If connection establishment time is a problem, make sure to activate a single master SSH connection and use slave mode for subsequent connections.

If latency is a problem, there's not much you can do except adapt your habits. If the latency is so high that interactive programs are painful to use, type commands locally and send them over when done (Emacs shell mode is nice for that). Do file management over SSHFS (except remote-to-remote copies).

Avoid needing remote X as it's both latency-sensitive and bandwidth-consuming. If you really must, NX is the best of the crop (but it's painful to set up because it's not free software so distributions don't provide it; this may change as free clones are emerging).

share|improve this answer

RSA keypairs are only for authentication and for exchange of symmetric keys, which is used for encryption of connection. You can try to use a symmetric cipher, which is not as hard for computation as default cipher is, i.e. blowfish. But this will not do with throughput, but with CPU utilization...

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.