Talk:Telnet

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Encryption[edit]

Telnet DOES support encryption. But it has to be negotiated for, and is not on by default (and not all clients and servers support it). But see, for example, http://www.faqs.org/rfcs/rfc2952.html and http://www.faqs.org/rfcs/rfc2953.html

Citations[edit]

I'm perfectly comfortable with the RFC's at the bottom of the article. Telnet was defined by RFC's and revised through RFC's. I think the two warning should be removed. — Preceding unsigned comment added by Gggustafson (talkcontribs) 21:34, 12 May 2015 (UTC)[reply]

Introduction[edit]

There's an incomplete sentence in the introduction. I'd fix it but I don't know what it's supposed to say.

"Most network equipment and operating systems with a configuration (including systems based on Windows NT)."

FalsePockets (talk) 01:20, 26 November 2015 (UTC)[reply]

Telnet in login[edit]

Telnet is used in the login page of many Broadband connections.

Shubhrajit Sadhukhan (talk) 05:20, 17 July 2020 (UTC)[reply]

Telnet is the name of a protocol + a service + a client[edit]

This article mixes the Telnet protocol, Telnet service, and Telnet client.

The Telnet protocol is used to transfer data between the console used and the remote server in both directions. These are e.g. terminal type, width and height of the window. This protocol is used by the telnet client and service, but also by SSH.

On the other hand, only the combination of Telnet service and Telnet client is outdated and insecure, because they transmit the data in plain text. Telnet over an SSH tunnel, on the other hand, is secure. — Preceding unsigned comment added by Lemmi18 (talkcontribs)

SSH communicates terminal type as part of the Secure Shell Connection Protocol, not with Telnet. Same for initial window width/height. I think resizes are handled by the terminal emulation itself, not by the encapsulating protocol. Telnet does have an option to communicate that information (what doesn't it have an option for), but I suspect it is done in practice by escape sequences handled by the terminal instead.
And I don't think the telnet service (and client combination) is insecure per se. If it provides shell access to a machine, sure, but the telnet service itself is merely a virtual teletype. It could provide text-based amusement services without any security impact, like a public non-secured BBS where anybody could dial in anyway. These can in fact still be found live on the internet.
If you think the article can be improved with a clearer separation of which parts of the text apply to protocol, service and client, go ahead. Although I'm having a bit of trouble mentally separating protocol from service. What is the service? The protocol encapsulates a teletype. A common service exposed on that protocol is a Unix shell, but the telnet service is not a Unix shell. Anything goes, your service could be an AAlib live transcoding of your favourite television channel. So what is the telnet service then? You might mention that due to how common it was for some time, people refer to a remote shell as the telnet service, but I think that is not actually what it is, just a common oversimplification based on what it had become by the time it got obsolete. But there was a time before that where it was just the TCP/IP-alternative to your telephone line modem, also something you used to dial in to a BBS rather than a Unix shell. Digital Brains (talk) 10:08, 23 October 2022 (UTC)[reply]