Thread: SSH Help
View Single Post
Old 02-21-2012, 04:42 PM   #71
knc1
Helpdesk Junkie
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 6,828
Karma: 6314522
Join Date: Feb 2012
Device: Too many.
Quote:
Originally Posted by geekmaster View Post
Yes, SSH over USB can be incredibly slow to connect on the DX and DXG as well as the K3. I usually just telnet in to save time.
- - snip - -
It was explained to me by another developer that this may be due to the version of openssl being used here requiring more CPU power than is available on these devices.
Close to most likely reason.

Subject came up this past week on the OpenSSL mailing list (again).

The most likely cause in these small, inactive, embedded devices is getting enough bytes out of /dev/random. Those bytes are needed while generating per-session keys, meaning the connection will not complete (whole process will stall) until /dev/random fills back up.
That can take a long time on an embedded device under Linux without other events happening.

Now if any reader here running into this "slow to connect" problem would just post the output of ssh -vv what-ever, we could see where the connection process is stalling.

Without the info from people having the problem we can only speculate.
knc1 is offline   Reply With Quote