| 1 |
On 25/06/2014 23:10, Stefan G. Weichinger wrote: |
| 2 |
> Am 25.06.2014 21:49, schrieb Alan McKinnon: |
| 3 |
> |
| 4 |
>> I've also noticed slowdowns recently, I think it's the new ciphers likes |
| 5 |
>> ecdsa. Try this: |
| 6 |
>> |
| 7 |
>> Connect using ssh -vvv and examine the output to find which of the |
| 8 |
>> various ciphers and algorithms are used once connection is achieved. On |
| 9 |
>> the client, add those configuration options for the server to |
| 10 |
>> ssh_config. You should notice a speed up on the next attempt as unused |
| 11 |
>> methods will be skipped |
| 12 |
>> |
| 13 |
>> man 5 ssh_config |
| 14 |
>> |
| 15 |
>> has all the details |
| 16 |
> |
| 17 |
> ;-) |
| 18 |
> |
| 19 |
> thanks, Alan. |
| 20 |
> |
| 21 |
> Did you already find out what options to set? |
| 22 |
|
| 23 |
No, only you can do that. You have to run ssh -vvv and eyeball the |
| 24 |
output, see what your machines are using. Then add those config settings |
| 25 |
to ssh_config |
| 26 |
|
| 27 |
> |
| 28 |
> Aside from that, I wonder why we as users have to do that and why it |
| 29 |
> isn't set up "as good as possible" by the coders of openssh. |
| 30 |
|
| 31 |
Because the openssh developers have no idea what you set up and cannot |
| 32 |
possibly know. The phrase "as good as possible" has no meaning here as |
| 33 |
the options out there in the wild as whatever they happen to be. |
| 34 |
|
| 35 |
|
| 36 |
> I will see if I can figure out what to do ... |
| 37 |
|
| 38 |
ssh -vvv |
| 39 |
|
| 40 |
then look |
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
|
| 45 |
-- |
| 46 |
Alan McKinnon |
| 47 |
alan.mckinnon@×××××.com |
Archives