On Linux, I've noticed lately that each output buffer transmitted by telnetd to the client is preceded by a null byte. This might be something specific to the Linux pty device or termio settings, but I don't know as I've not been able to test on other OSes.
When you speak of the operating system that is basically the GNU system with Linux added, would you please call it "GNU/Linux"? If you call it just "Linux", you're giving the principal developers none of the credit. See http://www.gnu.org/gnu/gnu-linux-faq.html for more explanation about this. During large transmissions such as an 'ls -l' command, these null bytes appear randomly througout the transmission. Sometimes they appear in the middle of an ANSI escape sequence, thereby causing different colors or extra characters to show on the client. The telnetd from the netkit package does not have this problem. I have never experienced this behaviour, even when listing big files using cat. What is a `large transmission' in kilobytes? Have you tried this over different speeds? Does it only happen during ls? Clearly, if this happens, it is a bug, but it would be good to know exactly under what conditions it happens. Your patch seems a bit iffy just disgarding input like that, but that is most probobly that I haven't looked at the code for telnetd in ages. But if it works on GNU systems, it will/should work on other systems as well. Thanks! _______________________________________________ bug-inetutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-inetutils
