|Device||Interface||IP Address||Subnet Mask|
Part 1: Secure Passwords
Part 2: Encrypt Communications
Part 3: Verify SSH Implementation
SSH should replace Telnet for management connections. Telnet uses insecure plain text communications. SSH provides security for remote connections by providing strong encryption of all transmitted data between devices. In this activity, you will secure a remote switch with password encryption and SSH.
- Using the command prompt on PC1, Telnet to S1. The user EXEC and privileged EXEC password is cisco.
- Save the current configuration so that any mistakes you might make can be reversed by toggling the power for S1.
- Show the current configuration and note that the passwords are in plain text. Enter the command that encrypts plain text passwords:
S1(config)# service password-encryption
- Verify that the passwords are encrypted.
- Set the IP domain name and generate secure keys.
It is generally not safe to use Telnet, because data is transferred in plain text. Therefore, use SSH whenever it is available.
- Configure the domain name to be netacad.pka.
S1(config)# ip domain-name netacad.pka
- Secure keys are needed to encrypt the data. Generate the RSA keys using a 1024 key length.
S1(config)# crypto key generate rsa
The name for the keys will be: S1.netacad.pka
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 : 1024
% Generating 1024 bit RSA keys, keys will be non-exportable…[OK]
- Create an SSH user and reconfigure the VTY lines
for SSH-only access.
- Create an administrator user with cisco as the secret password.
S1(config)# username administrator secret cisco
- Configure the VTY lines to check the local username database for login credentials and to only allow SSH for remote access. Remove the existing vty line password.
S1(config-line)# login local
S1(config-line)# transport input ssh
S1(config-line)# no password cisco
- Exit the Telnet session and attempt to log back in using Telnet. The attempt should fail.
- Attempt to log in using SSH. Type ssh and press Enter without any parameters to reveal the command usage instructions. Hint: The -l option is the letter “L”, not the number 1.
Upon successful login, enter privileged EXEC mode and save the configuration. If you were unable to successfully access S1, toggle the power and b