dropbear received data with bad writefd

[Prasad]

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
dropbearversion-0.48.

I have attached the log (running with debug enabled) with this mail.
Please let me know what i have missed. I will continue debugging
meanwhile.

Thanx
- Prasad

On 7/14/06, Matt Johnston <matt at ucc.asn.au> wrote:
> On Fri, Jul 14, 2006 at 11:54:40AM -0400, Jate Sujjavanich wrote:
> > I set up dropbear as a inetd service, and I can login. 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 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 when the server receives data on a
> channel that it thinks is already closed. Most likely it's a
> logic error somewhere in the channel handling code - I need
> to fix some things there.
>
>
> Cheers,
> Matt
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: debugtrace
Type: application/octet-stream
Size: 9012 bytes
Desc: not available
Url : http://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/attachments/20060717/320b40a0/debugtrace.obj