dropbear received data with bad writefd

[Jate Sujjavanich]

I am attempting to get Dropbear 0.47 working for m68knommu/Coldfire
working for uClinux. I configured with the 
--disable-openpty. I undefined HAVE_GETPTY.

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: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
 writefd
<6>Jul 14 11:45:02 dropbear[172]: Child connection from
192.168.120.6:52912

I get the following messages from the ssh client:

root at 192.168.121.37's password:
debug2: we sent a password packet, wait for reply
debug1: Authentication succeeded (password).
debug1: channel 0: new [client-session]
debug2: channel 0: send open
debug1: Entering interactive session.
debug2: callback start
debug2: client_session2_setup: id 0
debug2: channel 0: request pty-req confirm 0
debug2: channel 0: request shell confirm 0
debug2: fd 3 setting TCP_NODELAY
debug2: callback done
debug2: channel 0: open confirm rwindow 8000 rmax 8000
debug1: channel 0: free: client-session, nchannels 1
Connection to 192.168.121.37 closed by remote host.
Connection to 192.168.121.37 closed.
debug1: Transferred: stdin 0, stdout 0, stderr 91 bytes in 17.3 seconds
debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 5.2
debug1: Exit status -1

Do you have any suggestions?

- Jate S.