News for hackers. Stuff that matters.
Re:The 7-bit Internet by teddyh on Thursday July 11, 2013 @07:33AM (#6025440)
No, Telnet does not, in fact, intercept any character sequences unless when connecting to the telnet port (port 23).
Re:The 7-bit Internet by vidarh on Thursday July 11, 2013 @08:47AM (#6025682)
This is not true on the client I have on my OS X box at work, nor on my Debian and Ubuntu machines at home, nor, I believe, with pretty much any other telnet client I've used in the last twenty or so years. I just tested several to verify whether I'd somehow missed something so basic.

Regardless of the issue of negotiated options, most telnet clients goes into a command mode if you enter an escape character, defaulting to ctrl+], unless you explicitly change it or tell it not to with a command line switch. This happens for me regardless of port.

tcpdump and strace also confirms what I thought I knew, namely that it also does LF => CR+LF conversion also when connecting to other ports.

EDIT: Here's a simple demonstration of how it is decidedly not 8-bit clean:

    echo -e "test\035help" | telnet www.google.com 80
Not only will this get you the help text for telnet rather than send the unmodified byte stream to Google's unsuspecting web server, but with default options not a single byte will generally get sent over this connection on Linux at least, as the client starts out line buffered and gets put into command mode without getting a line feed.

Confirm with tcpdump, or this way if you have strace installed:

    echo -e "test\035help" | strace telnet www.google.com 80 2>&1 | grep sendto 
(the sendto calls you will get are DNS lookups)
Re:The 7-bit Internet by teddyh on Friday July 12, 2013 @03:20PM (#6034564)
Right, the interactive escape character. That's easily fixed with "telnet -E". That is,

    echo -e "test\035help" | telnet -E www.google.com 80
will not give any help text output.

(I was, in fact referring to telnet option negotiation which will not happen if not using the telnet port. Since the escape character for interactive use is so easily remedied, it did not occur to me to consider it a problem.)