exit after auth

Christian Ruppert idl0r at qasl.de
Sun Jun 27 07:28:42 WST 2010


On 06/26/2010 11:49 PM, Rob Landley wrote:
> On Saturday 26 June 2010 10:14:50 Christian Ruppert wrote:
>> Hey guys,
>>
>> I'm playing with my initramfs (busybox/glibc) but I have some trouble
>> with dropbear (0.52).
>> <snip>
>> dropbear[748]: Running in background
>> dropbear[749]: Child connection from ....
>> dropbear[749]: pubkey auth succeeded for ´root´ with key md5 ... from ...
>> dropbear[750]: Failed listening on ´22´: Error listening: Address
>> already in use
>> dropbear[750]: premature exit: No listening ports available.
>> dropbear[749]: exit after auth (root): Disconnect received
>> </snip>
> 
> "Trouble with dropbear" is kind of vague as a problem report goes.  It sounds 
> like this message happens not right after you run the dropbear server, but 
> when a child connects to it.  But that's just a guess, you never actually said 
> what you _did_.
I run dropbear in my initramfs.
dropbear is dynamic linked and without pam support.
All needed libraries are also in my initramfs.
I converted my openssh host keys with dropbearconvert.
/root/.ssh/authorized_keys exists and contains my public key.
host keys exists as /etc/dropbear/dropbear_rsa_host_key and
/etc/dropbear/dropbear_dss_host_key.

"dropbear" without parameter and "ssh root at host -i key"

> 
>> I receive the motd from dropbear and then got a disconnect.
> 
> So your child process did manage to connect to the server and got data from 
> it.  (Meaning the failed listening thing is probably a second, unrelated sys
> problem?)
>
The listening problem is gone now (Looks like it was really related to
the busybox problem I had).

The message came from dbmulti.c when I tried the multicall stuff.
"Make a symlink pointing at this binary with one of the following names
...."
I use it now again without multicall.


> It sounds like dropbear couldn't spawn the shell for your login process.  What 
> shell does your /etc/passwd entry for that user specify?
I tried /bin/sh as well as /bin/ash.

> 
> Rob

Attachments containing "strace -F -ff -o dropbear /sbin/dropbear -E -F
&> dropbear.log"
I hope it helps.
Maybe I overlooked something.

-- 
Regards,
Christian Ruppert
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dropbear.761
Url: http://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/attachments/20100627/b5d510f1/attachment-0002.txt 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dropbear.762
Url: http://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/attachments/20100627/b5d510f1/attachment-0002.asc 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dropbear.763
Url: http://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/attachments/20100627/b5d510f1/attachment-0003.txt 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dropbear.log
Url: http://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/attachments/20100627/b5d510f1/attachment-0003.asc 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
Url : http://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/attachments/20100627/b5d510f1/attachment-0001.pgp 


More information about the Dropbear mailing list