| gabriel rosenkoetter on Sun, 13 Apr 2003 19:11:44 -0400 |
|
On Sun, Apr 13, 2003 at 06:47:28PM -0400, Jeff Abrahamson wrote: > Logging in via ssh to a 486 box running debian sarge, there's a > significant pause, presumably to generate a new session key. This is > surely unavoidable short of new hardware. > > From the 486, I ssh to a very fast machine that, otherwise, would > respond almost instantly with a request for a password. But I get a 35 > second delay. Why would you expect different behavior from this interaction? *Both* sides need to do crypto work, and if you've got one side that does crypto work slowly, you're going to wait for awhile. You could change which cipher algorithm you use. See "Ciphers" in sshd_config(5), and do some background reading on which is likely to be fastest on your 486. (I've got a feeling that blowfish-cbc is probably your best bet, but I don't recall all the details. arcfour might not be bad either.) You can use the same variable name (see ssh_config(5); if you're using SSH-1, you actually want Cipher rather than Ciphers) in ssh_config (or ~/.ssh/config), and I *think* that the client gets its preference honored if the server's Ciphers setting permits it, but I'm not positive. -- gabriel rosenkoetter gr@eclipsed.net Attachment:
pgp07M0omVZ9A.pgp
|
|