Generate Ssh Rsa Key Cisco

I did a little research and found out that if I removed the rsa key by using this command ' crypto key zeroize rsa' and then added the 'crypto key generate rsa generate-keys modulus 1024, then that would work. Any thoughts? No service pad. No service password-encryption. Hostname Sales-SW-ACC2. Ip domain name my.company.come. Sep 26, 2017 - This lesson explains how to configure SSH Public Key Authentication on Cisco IOS using Windows and Linux.

Contents

Introduction

This document explains how to use the Key generator for PuTTY (PuTTYgen) to generate Secure Shell (SSH) authorized keys and RSA authentication for use on Cisco Secure Intrusion Detection System (IDS). The primary issue when you establish SSH authorized keys is that only the older RSA1 key format is acceptable. This means that you need to tell your key generator to create an RSA1 key, and you must restrict the SSH client to use the SSH1 protocol.

Prerequisites

Requirements

Generate Ssh Rsa Key Cisco

There are no specific requirements for this document.

Components Used

The information in this document is based on these software and hardware versions:

  • Recent PuTTY - February 7, 2004

  • Cisco Secure IDS

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

Refer to the Cisco Technical Tips Conventions for more information on document conventions.

Configure

This section presents you with the information to configure the features this document describes.

Note: Use the Command Lookup Tool (registered customers only) to find additional information on the commands this document uses.

Configure PuTTYgen

Complete these steps to configure PuTTYgen.

  1. Launch PuTTYgen. /elliptic-curve-cryptography-generate-public-key.html.

  2. Click the SSH1 key type and set the number of bits in the generated key to 2048 in the Parameters group at the bottom of the dialog box.

  3. Click Generate and follow the instructions.

    The key information is displayed in the upper section of the dialog box.

  4. Clear the Key Comment edit box.

  5. Select all the text in Public key for pasting into authorized_keys file and press Ctrl-C.

  6. Type a passphrase in the Key passphrase and Confirm passphrase edit boxes.

  7. Click Save private key.

  8. Save the PuTTY private key file into a directory private to your Windows login (in the Documents and Settings/(userid)/My Documents subtree in Windows 2000/XP).

  9. Launch PuTTY.

  10. Create a new PuTTY session as seen here:

    • Session:

    • IP Address: IP address of the IDS sensor

    • Protocol: SSH

    • Port: 22

    • Connection:

    • Auto-login username: cisco (can also be the login you use on the Sensor)

    • Connection/SSH:

    • Preferred SSH version: 1 only

    • Connection/SSH/Auth:

    • Private key file for authentication: Browse to the .PPK file stored in step 8.

    • Session: (back to the top)

    • Saved sessions: (enter the sensor name, click Save)

  11. Click Open and use password authentication to connect to the Sensor CLI, since the public key is not on the Sensor yet.

  12. Enter the configure terminal CLI command and press Enter.

  13. Enter the ssh authorized-key mykey CLI command, but do not press Enter at this time. Make sure and type a space at the end.

  14. Right-click in the PuTTY terminal window.

    The clipboard material copied in step 5 is typed into the CLI.

  15. Press Enter.

  16. Enter the exit command and press Enter.

  17. Confirm the authorized key is entered properly. Enter the show ssh authorized-keys mykey command and press Enter.

  18. Enter the exit command to quit the IDS CLI and press Enter.

Verify

RSA Authentication

Complete these steps.

  1. Launch PuTTY.

  2. Locate the Saved Session created in step 10 and double-click on it. A PuTTY terminal window opens and this text appears:

  3. Type the private key passphrase you created in step 6 and press Enter.

    You are automatically logged in.

Troubleshoot

There is currently no specific troubleshooting information available for this configuration.

Related Information

  • October 2, 2015
  • Posted by: Syed Shujaat
  • Category: Cisco, Networking Solutions

Use this command to generate RSA key pairs for your Cisco device (such as a router). keys are generated in pairs–one public RSA key and one private RSA key.

If your router already has RSA keys when you issue this command, you will be warned and prompted to replace the existing keys with new keys.

NOTE: Before issuing this command, ensure that your router has a hostname and IP domain name configured (with the hostname and ipdomain-name commands).

You will be unable to complete the cryptokeygeneratersacommand without a hostname and IP domain name. (This situation is not true when you generate only a named key pair.)

Here are the steps to Enable SSH and Crypto Key setup : 2 config must requried for SSH

1 Setup Local VTY line User ID and password

router (Config) # Line VTY 0 15

router (Config-line)# login local

router (Config-line)# Exit

!!! create local login ID/Pass

router (Config)# username [loginid] password [cisco]

router (Config)# username loginid1 password cisco1

2. router (Config)# ip domain-name example.com

router (Config)# crypto key generate rsa

how many bits in the modulus [512] :1024

router (Config)# ip ssh version2

Cisco Generate Rsa Key For Ssh

router (Config)# CTRL Z


Note

Secure Shell (SSH) may generate an additional RSA key pair if you generate a key pair on a router having no RSA keys. The additional key pair is used only by SSH and will have a name such as {router_FQDN }.server.

/grand-ages-rome-cd-key-generator.html. For example, if a router name is “router1.cisco.com,” the key name is “router1.cisco.com.server.”

This command is not saved in the router configuration; however, the RSA keys generated by this command are saved in the private configuration in NVRAM (which is never displayed to the user or backed up to another device) the next time the configuration is written to NVRAM.

Modulus Length

When you generate RSA keys, you will be prompted to enter a modulus length. The longer the modulus, the stronger the security. However, a longer modules take longer to generate (see the table below for sample times) and takes longer to use.

The size of Key Modulus range from 360 to 2048. Choosing modulus greater than 512 will take longer time.

Router360 bits512 bits1024 bits2048 bits (maximum)
Cisco 250011 seconds20 seconds4 minutes, 38 secondsMore than 1 hour
Cisco 4700Less than 1 second1 second4 seconds50 seconds

Cisco IOS software does not support a modulus greater than 4096 bits. A length of less than 512 bits is normally not recommended. In certain situations, the shorter modulus may not function properly with IKE, so we recommend using a minimum modulus of 2048 bits.

Create Rsa Ssh Key

Syntax Description : Optional Strings to embed with SSH Crypto key

general-keys(Optional) Specifies that a general-purpose key pair will be generated, which is the default.
usage-keys(Optional) Specifies that two RSA special-usage key pairs, one encryption pair and one signature pair, will be generated.
signature(Optional) Specifies that the RSA public key generated will be a signature special usage key.
encryption(Optional) Specifies that the RSA public key generated will be an encryption special usage key.
labelkey-label(Optional) Specifies the name that is used for an RSA key pair when they are being exported.If a key label is not specified, the fully qualified domain name (FQDN) of the router is used.
exportable(Optional) Specifies that the RSA key pair can be exported to another Cisco device, such as a router.
modulusmodulus-size(Optional) Specifies the IP size of the key modulus.By default, the modulus of a certification authority (CA) key is 1024 bits. The recommended modulus for a CA key is 2048 bits. The range of a CA key modulus is from 350 to 4096 bits.
Note Effective with Cisco IOS XE Release 2.4 and Cisco IOS Release 15.1(1)T, the maximum key size was expanded to 4096 bits for private key operations. The maximum for private key operations prior to these releases was 2048 bits.
storagedevicename:(Optional) Specifies the key storage location. The name of the storage device is followed by a colon (:).
redundancy(Optional) Specifies that the key should be synchronized to the standby CA.
ondevicename:(Optional) Specifies that the RSA key pair will be created on the specified device, including a Universal Serial Bus (USB) token, local disk, or NVRAM. The name of the device is followed by a colon (:).Keys created on a USB token must be 2048 bits or less.

How To Generate Ssh Key Cisco

CommandDescription
copyCopies any file from a source to a destination, use the copy command in privileged EXEC mode.
cryptokeystorageSets the default storage location for RSA key pairs.
debugcryptoengineDisplays debug messages about crypto engines.
hostnameSpecifies or modifies the hostname for the network server.
ipdomain-nameDefines a default domain name to complete unqualified hostnames (names without a dotted-decimal domain name).
showcryptokeymypubkeyrsaDisplays the RSA public keys of your router.
show crypto pki certificatesDisplays information about your PKI certificate, certification authority, and any registration authority certificates.