On Thu, Aug 17, 2006 at 04:10:59AM -0700, Haseeb Abdul Qadir wrote:
> Hi,
>
> When using dropbear for port forwarding only (no command shell, no pty) the
> sever sometimes unexpectedly exits with:
>
> [21929] Aug 17 06:29:01 exit after auth (haseebq): received data with bad
Hi,When using dropbear for port forwarding only (no command shell, no pty) the sever sometimes unexpectedly exits with:[21929] Aug 17 06:29:01 exit after auth (haseebq): received data with bad writefd
Its not a 100% repro but I have seen it happen a few times. Any idea how I'd diagnose this?T
17, 2006 2:22 PM
To: dropbear@ucc.asn.au
Subject: Re: dropbear received data with bad writefd
Hi matt,
I also got the same kinda error after i get the login and enter passwd.
My platform is uClinux+microblaze. I moved from the default dropbear
version in uClinux (0.43 which worked perfect) to drop
n. When the
> > shell is supposed to come up, I get the following messages from the
> > dropbear server log:
> >
> > <6>Jul 14 11:44:59 dropbear[171]: exit after auth (root): received
> > data with bad writefd
>
> Could you compile Dropbear with DEBUG_TRACE en
supposed to come up, I get the following messages from the dropbear
> server log:
>
> <6>Jul 14 11:44:59 dropbear[171]: exit after auth (root): received data
> with bad
> writefd
Could you compile Dropbear with DEBUG_TRACE enabled in
debug.h, and run it as a standalone server
auth (root): received data
> with bad
> writefd
Could you compile Dropbear with DEBUG_TRACE enabled in
debug.h, and run it as a standalone server and with the -v
flag? That should give a bit more detail.
The output of ssh -vvv for the client might also be useful.
The error message occurs wh
server log:
<6>Jul 14 11:44:20 dropbear[171]: Child connection from
192.168.120.6:52911
<5>Jul 14 11:44:54 dropbear[171]: password auth succeeded for 'root'
from 192.16
8.120.6:52911
<6>Jul 14 11:44:59 dropbear[171]: exit after auth (root): received data
with bad
