PuTTYgen Generation of SSH Authorized Keys and RSA Authentication on Cisco Secure IDS Configuration Example. 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. There are no specific requirements for this document. 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. Refer to the Cisco Technical Tips Conventions for more information on document conventions. 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. Complete these steps to configure PuTTYgen. 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. Click Generate and follow the instructions. The key information is displayed in the upper section of the dialog box. Clear the Key Comment edit box. Select all the text in Public key for pasting into authorized_keys file and press Ctrl-C. Type a passphrase in the Key passphrase and Confirm passphrase edit boxes. Click Save private key. 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. Create a new PuTTY session as seen here.
PREVIOUS NEXT