The following lines were added (+) and removed (-):
== telnet ==We've already mentioned the lack of security. Quote, "The telnet daemons (the process that sits on the server and processes your login) have had numerous vunerabilities and will continue to have them. Running telnetd is just one more old daemon waiting to be used to crack your machine!" from the post [https://www.linuxquestions.org/questions/linux-networking-3/why-you-should-use-ssh-instead-of-telnet-388664/ Why you should use ssh instead of telnet].There are times when telnet may be useful. On a private LAN (no route to the Internet) or a connection between two machines only (ultra private LAN) the use of telnet is acceptable, quick, and convenient. Furthermore, exploration on exactly how ssh is more secure, and where it is not can find validation in the use of telnet. One of the key advantages of SSH over telnet is that the server authenticates itself to the client before it collects credentials from the client. Most sniffing occurs within the network itself and not outside of the router. Common ssh installations ignore precautions that protect against external threats, making those networks no more secure when using ssh versus telnet. If there is no threat within the network itself, all traffic tunnelled to a remote network within a secure VPN, and concluding there is no internal threat within that remote network, telnet would offer no lessor security as compared to ssh in the described scenario.