[BusyBox] telnetd with busybox-sh

[David Kimdon]

This is due to sash being able to handle getting random control characters
spewed at it better than busybox sh.  This is fixed in a patch that I sent
to the list:
http://busybox.net/lists/busybox/2001-August/004262.html

The new funciton of interest is remove_iac().

BTW. How do people like telnetd, should I apply this?  I haven't gotten a
definitive answer.

-David

Wed, Aug 22, 2001 at 05:30:03PM +0200 wrote:
> Hi,
> 
> I am running Busybox 0.52 on a PowerPC target. I compiled the simple
> telnetd from the tinylogin CVS directory for that system. As long as I
> use sash as login shell for telnetd everything is fine. When I use
> /bin/sh (busybox shell, msh) as shell, the telnet client screen gets
> full of wild characters and the shell cannot be used ! What is tzhe
> reason for this problem ?
> 
> Matthias
> 
> 
> _______________________________________________
> busybox mailing list
> busybox at busybox.net
> http://busybox.net/mailman/listinfo/busybox