Re: 45s login delay

2011-03-17 Thread Matt Johnston
On Wed, Mar 16, 2011 at 07:16:34PM -0500, Rob Landley wrote: On 03/16/2011 02:25 AM, Peter Turczak wrote: Hi Magnus, hi Rob, a while ago I made the same observations you did. On an m68k-nommu with 166 MHz the RSA exchange took quite forever. After some profiling I found out the comba

Re: 45s login delay

2011-03-16 Thread Peter Turczak
Hi Magnus, hi Rob, a while ago I made the same observations you did. On an m68k-nommu with 166 MHz the RSA exchange took quite forever. After some profiling I found out the comba multiply routine in libtommath was eating most of the time. It seems gcc produces quite inefficient code there.

Re: 45s login delay

2011-03-16 Thread Rob Landley
On 03/16/2011 02:25 AM, Peter Turczak wrote: Hi Magnus, hi Rob, a while ago I made the same observations you did. On an m68k-nommu with 166 MHz the RSA exchange took quite forever. After some profiling I found out the comba multiply routine in libtommath was eating most of the time. It

Re: 45s login delay

2011-03-15 Thread Magnus Nilsson
Sorry, I was unclear - it's only 100% busy during those 45s. This is what it looks like if I first start the load monitor (-r outputs 1 sample/second), then start to log in from a remote ssh client: # cpu -r CPU: busy 0% (system=0% user=0% nice=0% idle=100%) CPU: busy 24% (system=4%

Re: 45s login delay

2011-03-15 Thread Olof Kindgren
Hi, I don't have any real numbers right now, but it takes roughly a minute on a 10MHz OpenRISC CPU, so it seems something is up //Olof 2011/3/15 Matt Johnston m...@ucc.asn.au On Tue, Mar 15, 2011 at 02:02:54PM +0100, Magnus Nilsson wrote: Sorry, I was unclear - it's only 100% busy during

Re: 45s login delay

2011-03-15 Thread Peter Korsgaard
Magnus == Magnus Nilsson m...@lundinova.se writes: Hi, Magnus Is 45s reasonable on a 192MHz cpu, or do you think I might have Magnus some issue with my compilation options Here it takes ~1s on a 400MHz ARM9 so I doubt it. -- Bye, Peter Korsgaard

Re: 45s login delay

2011-03-15 Thread Rob Landley
On 03/15/2011 08:02 AM, Magnus Nilsson wrote: Sorry, I was unclear - it's only 100% busy during those 45s. This is what it looks like if I first start the load monitor (-r outputs 1 sample/second), then start to log in from a remote ssh client: # cpu -r CPU: busy 0% (system=0% user=0%

45s login delay

2011-03-14 Thread Magnus Nilsson
Hello, I have an issue with ~45s delay on every login (ssh, scp etc). Once the link is up dropbear runs fine. After reading these forums, I have disabled reverse lookup and added client IP to /etc/hosts, but that didn't help. I'm running dropbear 0.53.1 on armv4tl, uClinux 2.6.19, built

Re: 45s login delay

2011-03-14 Thread Magnus Nilsson
Hi, Thanks for the quick reply. It's at 192MHz. It's this one: http://www.moxa.com/product/EM-1240.htm If this is expected, what can I do to shorten the delay (without compromising security too much)? 45s is a bit long to endure (e.g. WinSCP gives up after 15s). I'll try get top or a better

Re: 45s login delay

2011-03-14 Thread Magnus Nilsson
You mean like 'ssh -c 3des root@10.240.22.103'? (I also deleted /etc/dropbear_rsa_host_key to be sure) Unfortunately I get the exact same delay - 45s. Kind regards/Magnus On 2011-03-14 13:27, Matt Johnston wrote: If you only give the server a DSS key how does it perform? That should be

Re: 45s login delay

2011-03-14 Thread Rob Landley
On 03/14/2011 10:09 AM, Magnus Nilsson wrote: Both top and ps are the gimped uClinux versions, but I found the cpu tool: # cpu -r CPU: busy 100% (system=0% user=99% nice=0% idle=0%) CPU: busy 100% (system=0% user=100% nice=0% idle=0%) ... So indeed it looks busy. Any