Skip to main content

What is Secure Shell (SSH) and how to configure SSH in Cisco Devices

What is Secure Shell (SSH) and how to configure SSH in Cisco Devices

What is Secure Shell (SSH)
Secure Shell is a protocol that can be used in the place of well known Telnet protocol to remotely connect to your Cisco Router or Switch. Telnet has long been used to manage network devices; however, Telnet traffic is sent in clear text. Anyone able to sniff that traffic would see your password and any other information sent during the Telnet session. Secure Shell (SSH) is a much more secure way to manage your routers and switches. It is a client/server protocol that encrypts the traffic in and out through the vty ports.
Cisco routers and switches can act as SSH clients by default, but must be configured to be SSH servers. That is, they can use SSH when connecting to another device, but require configuration before allowing devices to connect via SSH to them. They also require some method of authenticating the client. This can be either a local username and password, or authentication with a AAA server (AAA is detailed in the next section).
There are two versions of SSH. SSH Version 2 is an IETF standard that is more secure than version 1. Version 1 is more vulnerable to man-in-the-middle attacks, for instance. Cisco devices support both types of connections, but you can specify which version to use.
How to Configure SSH in Cisco Devices
Telnet is enabled by default, but configuring even a basic SSH server requires several following steps:
1. Ensure that your IOS supports SSH. You need a K9 image for this.
2. Configure a host name.
3. Configure a domain name.
4. Configure a client authentication method.
5. Tell the router or switch to generate the Rivest, Shamir, and Adelman (RSA) keys that will be used to encrypt the session.
6. Specify the SSH version, if you want to use version 2.
7. Disable Telnet on the VTY lines.
8. Enable SSH on the VTY lines.
Here are the configuration command to configure Secure Shell on Cisco Routers or Switches
router(config)# hostname R1
R1(config)# ip domain-name networkpcworld
R1(config)# username cisco password Cisco
R1(config)# crypto key generate rsa
The name for the keys will be: R1.networkpcworld
Choose the size of the key modulus in the range of 360 to 2048 for your General Purpose Keys. Choosing a key modulus greater than 512 may take a few minutes.
How many bits in the modulus [512]: 1024
% Generating 1024 bit RSA keys …[OK]
R1(config)#
*May 22 02:06:51.923: %SSH-5-ENABLED: SSH 1.99 has been enabled
R1(config)# ip ssh version 2
!
R1(config)# line vty 0 4
R1(config-line)# transport input none
R1(config-line)# transport input ssh
R1(config-line)#^Z
!
R1# show ip ssh
SSH Enabled – version 2.0
Authentication timeout: 120 secs; Authentication retries: 3
Labels:

Comments

Post a Comment

Popular posts from this blog

How to import Putty Saved Connections to mRemoteNG

Just started using mRemoteNG and its being very cool to connect to different remote connection with different protocols e.g Window Remote Desktop, VNC to Linux, SSH, HTTP connection etc. from a single application. As new user I configured some remote desktop connection which was quite easy to figure out. But when I wanted to add SSH connections, it came in my mind to import all of the saved connections in the putty. But I couldn't figure it out how can it be done, though it was quite easy and here are the steps. Open your mRemoteNG Create a folder if you want segregation of multiple networks Create a new connection Enter the IP address of remote server under connection in Config pane Under the config pane, select protocol " SSH version 2 ".  Once you select protocol to SSH version 2 you are given option to import putty sessions, as shown in the snap below. In the above snap, I have imported CSR-AWS session from my saved sessions in Putty.
1 comment
Read more

Authoritative DNS Servers Delegation and Internal DNS Explained

DNS (Domain Name System) plays a critical role in how users and systems find resources on the internet or within internal networks. Whether it's managing an internal domain in an enterprise or delegating parts of a domain for traffic distribution, DNS setups vary widely depending on needs. In this blog post, we’ll break down the different types of DNS setups, including authoritative DNS servers, DNS delegation, and how internal DNS functions within organizations. 1. Authoritative DNS Server An Authoritative DNS server is the final source of truth for a specific domain. When someone queries a domain (e.g., example.com ), the authoritative DNS server for that domain holds the DNS records (A records, CNAME, MX, etc.) and responds with the corresponding IP address. Key Points: Who can host it? Authoritative DNS servers are often hosted by domain registrars (e.g., GoDaddy, Namecheap) or cloud DNS providers (e.g., AWS Route 53, Cloudflare). However, organizations can also host their ...
Post a Comment
Read more

SSL VPN vs IPSec VPN: Understanding the Key Differences

When it comes to securing communication over the internet, Virtual Private Networks (VPNs) are a cornerstone of modern networking. Two popular types of VPNs are SSL VPN and IPSec VPN . While both serve to encrypt and secure data, they differ significantly in terms of technology, use cases, and implementation. This blog post will help you understand these differences and choose the right solution for your needs. What is SSL VPN? An SSL VPN uses the Secure Sockets Layer (SSL) or its successor, Transport Layer Security (TLS) , to create a secure connection. It operates at the Application Layer (Layer 7) of the OSI model and is designed to provide secure access to specific resources over the internet. Key Features of SSL VPN: Ease of Use: Accessible via a standard web browser without the need for dedicated client software. Granular Access Control: Allows users to access specific applications or resources rather than the entire network. Port Usage: Uses TCP port 443, which is rarely...
Post a Comment
Read more