| 1 |
On 25/06/2014 20:41, Stefan G. Weichinger wrote: |
| 2 |
> Am 25.06.2014 20:30, schrieb James: |
| 3 |
>> Stefan G. Weichinger <lists <at> xunil.at> writes: |
| 4 |
>> |
| 5 |
>> |
| 6 |
>>> When I ssh into a server in my basement, this takes way more time than |
| 7 |
>>> usual. |
| 8 |
>>> Does anyone have an idea what I could do to fix that? |
| 9 |
>> |
| 10 |
>> |
| 11 |
>> ssh has an ordered array of negotiations between systems that are related |
| 12 |
>> to the version numbers of ssh and the other configurations. There is |
| 13 |
>> usually a mismatch, when it takes "too long" to start a session, |
| 14 |
>> in my experience. |
| 15 |
>> |
| 16 |
>> I did not look at the specifics you posted. |
| 17 |
> |
| 18 |
> both servers/machines run net-misc/openssh-6.6.1_p1 ... re-compiled |
| 19 |
> right today. |
| 20 |
|
| 21 |
I've also noticed slowdowns recently, I think it's the new ciphers likes |
| 22 |
ecdsa. Try this: |
| 23 |
|
| 24 |
Connect using ssh -vvv and examine the output to find which of the |
| 25 |
various ciphers and algorithms are used once connection is achieved. On |
| 26 |
the client, add those configuration options for the server to |
| 27 |
ssh_config. You should notice a speed up on the next attempt as unused |
| 28 |
methods will be skipped |
| 29 |
|
| 30 |
man 5 ssh_config |
| 31 |
|
| 32 |
has all the details |
| 33 |
|
| 34 |
|
| 35 |
|
| 36 |
-- |
| 37 |
Alan McKinnon |
| 38 |
alan.mckinnon@×××××.com |
Archives