[uClibc] dropbear config

[Rich Ireland]

Rob Landley wrote:
> On Thursday 17 February 2005 11:06 am, Rich Ireland wrote:
>>
>>After looking over the dropbear code, almost it looks like it's not
>>connecting the session to a login/tty process.  The client side is quite
>>happy to sit forever connected to dropbear without a login - no timeouts
>>or errors until I kill the dropbear process on the target.
> 
> I hadn't noticed earlier that you were using devfs.  I'm always amazed when 
> anyone can get that to work even briefly.  I'm guessing you're going to have 
> to either strace dropbear or stick printfs in it to figure out <strike>how 
> devfs is to blame</strike> what the actual problem is. :)

It appears that dropbear hangs right after identifying the client app. 
Interestingly, the next call in line is seed_random().

So, after changing options.h to use /dev/urandom instead of /dev/random, 
dropbear seems to work just fine.  It's slow, but it works.

Would anyone have any comments/suggestions on adding dropbear options to 
the uClibc buildroot config?

Thanks for all the help.

-- 
Rich Ireland
Firmware Engineer - Perforce Advocate
Idaho Technology, Inc.
http://www.idahotech.com/
mailto:rich.ireland at idahotech.com