Secure Shell Versus Telnet

Many network engineers commonly use Telnet to remotely connect to their routers; however, Cisco strongly recommends using Secure Shell (SSH) instead of Telnet.

The issue with Telnet is that it sends data (including passwords) across a network in clear text. This opens the door for a malicious user to launch a man-in-middle attack and use packet capture software to read the contents of the Telnet session’s packets.

Fortunately, SSH encrypts this traffic. So, even if a malicious user did capture packets from the SSH session, the packets would be unreadable.

The steps to configure SSH on a router are as follows:

Image

Step 1. ...

Get CCNP Routing and Switching ROUTE 300-101 Official Cert Guide now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.