While Encrypting a File with a Password from the Command Line using OpenSSLis very useful in its own right, the real power of the OpenSSL library is itsability to support the use of public key cryptograph for encrypting orvalidating data in an unattended manner (where the password is not required toencrypt) is done with public keys.

• Create Rsa Ssh Key
• Crypto Key Generate Rsa Command

The Commands to Run

Generate a 2048 bit RSA Key

Configuring key lengths: The crypto key generate ssh command allows you to specify the type and length of the generated host key. The size of the host key is platform-dependent as different switches have different amounts of processing power. Jun 28, 2007  If your SSH configuration commands are rejected as illegal commands, you have not successfully generated a RSA key pair for your router. Make sure you have specified a host name and domain. Then use the crypto key generate rsa command to generate an RSA key pair and enable the SSH server. The crypto key generates RSA command is something that will be dependent on the IP domain name commands and the hostname. The crypto command can be used in order to generate a key pair which will have a private and public RSA key. I'm setup an asr9010, but cannot ssh to it and cannot use 'crypto key gen rsa' command. Please kindly help to take a look. Every time I tried to login, the log shows 'SSHD65713:%SECURITY-SSHD-3-ERRGENERAL: Failed No Host Key configured on the device ' And I tried to use 'crypto key generate rsa' command but cannot find it.

You can generate a public and private RSA key pair like this:

openssl genrsa -des3 -out private.pem 2048

That generates a 2048-bit RSA key pair, encrypts them with a password you provideand writes them to a file. You need to next extract the public key file. You willuse this, for instance, on your web server to encrypt content so that it canonly be read with the private key.

Export the RSA Public Key to a File

This is a command that is

openssl rsa -in private.pem -outform PEM -pubout -out public.pem

The -pubout flag is really important. Be sure to include it.

Next open the public.pem and ensure that it starts with-----BEGIN PUBLIC KEY-----. This is how you know that this file is thepublic key of the pair and not a private key.

To check the file from the command line you can use the less command, like this:

less public.pem

Do Not Run This, it Exports the Private Key

A previous version of the post gave this example in error.

openssl rsa -in private.pem -out private_unencrypted.pem -outform PEM

The error is that the -pubout was dropped from the end of the command.That changes the meaning of the command from that of exporting the public keyto exporting the private key outside of its encrypted wrapper. Inspecting theoutput file, in this case private_unencrypted.pem clearly shows that the keyis a RSA private key as it starts with -----BEGIN RSA PRIVATE KEY-----.

Create Rsa Ssh Key

Visually Inspect Your Key Files

It is important to visually inspect you private and public key files to makesure that they are what you expect. OpenSSL will clearly explain the nature ofthe key block with a -----BEGIN RSA PRIVATE KEY----- or -----BEGIN PUBLIC KEY-----.

You can use less to inspect each of your two files in turn:

• less private.pem to verify that it starts with a -----BEGIN RSA PRIVATE KEY-----
• less public.pem to verify that it starts with a -----BEGIN PUBLIC KEY-----

The next section shows a full example of what each key file should look like.

The Generated Key Files

The generated files are base64-encoded encryption keys in plain text format.If you select a password for your private key, its file will be encrypted withyour password. Be sure to remember this password or the key pair becomes useless.

The private.pem file looks something like this:

The public key, public.pem, file looks like:

Protecting Your Keys

Depending on the nature of the information you will protect, it’s important tokeep the private key backed up and secret. The public key can be distributedanywhere or embedded in your web application scripts, such as in your PHP,Ruby, or other scripts. Again, backup your keys!

Remember, if the key goes away the data encrypted to it is gone. Keeping aprinted copy of the key material in a sealed envelope in a bank safety depositbox is a good way to protect important keys against loss due to fire or harddrive failure.

Oh, and one last thing.

If you, dear reader, were planning any funny business with the private key that I have just published here. Know that they were made especially for this series of blog posts. I do not use them for anything else.

Found an issue?

Rietta plans, develops, and maintains applications.

Learn more about our services or drop us your email and we'll e-mail you back.

Crypto Key Generate Rsa Command

Other Blog Articles Published by Rietta.com

1. Assign a local login (operator) and enable (manager) password.

   At a minimum, HP recommends that you always assign at least a manager password to the switch. Otherwise, under some circumstances, anyone with Telnet, web, or serial port access could modify the switch configuration.

   To configure local passwords:

   You can configure both the operator and manager password with one command.

   Syntax:

   Configuring local passwords

2. Generate the switch public and private key pair.

   A public and private host key pair must be generated on the switch. The switch uses this key pair along with a dynamically generated session key pair to negotiate an encryption method and session with an SSH client trying to connect to the switch.

   The host key pair is stored in the switch flash memory, and only the public key in this pair is readable. The public key should be added to a 'known hosts' file (for example, $HOME/.ssh/known_hosts on UNIX systems) on the SSH clients which should have access to the switch. Some SSH client applications automatically add the switch public key to a 'known hosts' file. Other SSH applications require you to manually create a known hosts file and place the switch public key in the file. See the documentation for your SSH client application for more details.

   (The session key pair mentioned above is not visible on the switch. It is a temporary, internally generated pair used for a particular switch/client session, and then discarded.)

   NOTE: When generating a host key pair on the switch, the switch places the key pair in flash memory and not in the running-config file. Also, the switch maintains the key pair across reboots, including power cycles. Consider this key pair to be 'permanent' and avoid re-generating the key pair without a compelling reason. Otherwise, you must re-introduce the switch public key on all management stations you have set up for SSH access to the switch using the earlier pair. Removing (zeroing) the switch public/private key pair renders the switch unable to engage in SSH operation and automatically disables IP SSH on the switch. To verify whether SSH is enabled, execute show ip ssh. However, any active SSH sessions will continue to run, unless explicitly terminated with the CLI kill command. To generate or erase the switch public/private host key pair:

   Because the host key pair is stored in flash instead of the running-config file, it is not necessary to use write memory to save the key pair. Erasing the key pair automatically disables SSH.

   Syntax:

   crypto key generate <autorun-key[rsa] cert[rsa] <keysize> [ssh][dsa rsa]bits <keysize>>

   Installs authentication files for ssh or https server, or for autorun.

   Install RSA key for autorun. See 'Configuring Autorun on the Switch' in the Management and Configuration Guide for more information.

   Install RSA key for https certificate.

   Use your SSL enabled browser to access the switch using the switch IP address or DNS name (if allowed by your browser). See the documentation provided with the browser application for more information.

   Install host key for ssh server. Specify the key type as DSA or RSA.

   Specify the key size (in bits).

   zeroize <ssh cert autorun[rsa]>

   Erases the switch public/private key pair and disables SSH operation.

   Displays switch public key. Displays the version 1 and version 2 views of the key.

   See SSH client public-key authentication for information about public keys saved in a configuration file.

   Displays hashes of the switch public key in phonetic format, see “Displaying the Public Key:”.

   Displays fingerprints of the switch public key in hexadecimal format, see “Displaying the Public Key:”.

   Example:

   To generate and display a new key:

   Example of generating a public/private host key pair for the switch

   To compare the switch key to the key stored in your client's known-hosts file, note that the formatting and comments need not match.

   NOTE: 'Zeroizing' the switch key automatically disables SSH (sets ip ssh to no). Thus, if you zeroize the key and then generate a new key, you must also re-enable SSH with the ip ssh command before the switch can resume SSH operation.

   Configuring key lengths:

   The crypto key generate ssh command allows you to specify the type and length of the generated host key. The size of the host key is platform-dependent as different switches have different amounts of processing power. The size is represented by the <keysize> parameter and has the values shown in . The default value is used if keysize is not specified.

   RSA/DSA values for various HP networking switches

   Platform	Maximum RSA Key Size (in bits)	DSA Key Size (in bits)
   5400/3500/6200/8200/2900	1024, 2048, 3072 Default: 2048	1024
   4200/2900/2810/2610/2510	1024, 2048 Default: 2048	1024
   5300/2800/3400/2600	896	512

3. Provide the switch public key to clients.

   When an SSH client contacts the switch for the first time, the client will challenge the connection unless you have already copied the key into the client's 'known host' file. Copying the switch key in this way reduces the chance that an unauthorized device can pose as the switch to learn your access passwords. The most secure way to acquire the switch public key for distribution to clients is to use a direct, serial connection between the switch and a management device (laptop, PC, or UNIX workstation), as described below.

   The public key generated by the switch consists of three parts, separated by one blank space each:

   A public key generated by the switch

   With a direct serial connection from a management station to the switch:

   1. Use a terminal application such as HyperTerminal to display the switch public key with the show crypto host public-key command, see Example of generating a public/private host key pair for the switch.

   2. Bring up the SSH client's 'known host' file in a text editor such as Notepad as straight ASCII text, and copy the switch public key into the file.

   3. Ensure that there are no changes or breaks in the text string. A public key must be an unbroken ASCII string. Line breaks are not allowed (changes in the line breaks will corrupt the Key.) For example, if you are using Windows® Notepad, ensure that Word Wrap (in the Edit menu) is disabled, and that the key text appears on a single line.

      Example of a correctly formatted public key

   4. Add any data required by your SSH client application. For example, before saving the key to an SSH client's 'known hosts' file you may have to insert the switch IP address:

      Example of a switch public key edited to include the switch’s IP address

      For more on this topic, see the documentation provided with your SSH client application.

   Displaying the Public Key:

   The switch provides three options for displaying its public key. This is helpful if you need to visually verify that the public key the switch is using for authenticating itself to a client matches the copy of this key in the client's 'known hosts' file:

   Key generator for games. Jan 23, 2015  Football Manager 2015 Key Generator No Survey. Football Manager 2015 allows you to live the life of a real football manager at where you decide who plays and who sits on the bench, and you’re in total control of tactics, team-talks, substitutions, and pitch-side instructions as you follow the match live with the acclaimed 3D match engine.

   • Non-encoded ASCII numeric string:

     Requires a client ability to display the keys in the 'known hosts' file in the ASCII format. This method is tedious and error-prone due to the length of the keys. See Example of a correctly formatted public key.

   • Phonetic hash:

     Outputs the key as a relatively short series of alphabetic character groups. Requires a client ability to convert the key to this format.

   • Hexadecimal hash:

     Outputs the key as a relatively short series of hexadecimal numbers. Requires a parallel client ability.

   For example, on the switch, generate the phonetic and hexadecimal versions of the switch public key as follows:

   Visual phonetic and hexadecimal conversions of the switch public key

   The two commands shown in Visual phonetic and hexadecimal conversions of the switch public key convert the displayed format of the switch (host) public key for easier visual comparison of the switch public key to a copy of the key in a client's 'known host' file. The switch has only one RSA host key. The 'babble' and 'fingerprint' options produce two hashes for the key--one that corresponds to the challenge hash you will see if connecting with a v1 client, and the other corresponding to the hash you will see if connecting with a v2 client. These hashes do not correspond to different keys, but differ only because of the way v1 and v2 clients compute the hash of the same RSA key. The switch always uses an ASCII version of its public key, without babble or fingerprint conversion, for file storage and default display format.

4. Enable SSH on the switch and anticipate SSH client contact behavior.

   The ip ssh command enables or disables SSH on the switch, and modifies parameters the switch uses for transactions with clients. After you enable SSH, the switch can authenticate itself to SSH clients.

   NOTE: Before enabling SSH on the switch you must generate the switch public/private key pair. If not yet done, see Generate the switch public and private key pair. When configured for SSH, the switch uses its host public key to authenticate itself to SSH clients.For SSH clients to authenticate themselves to the switch, configure SSH on the switch for client public-key authentication at the login (operator) level. To enhance security also configure local, TACACS+, or RADIUS authentication at the enable (manager) level. See Step 5.

   SSH client contact behavior:

   At the first contact between the switch and an SSH client, if the switch public key has not been copied into the client, then the client's first connection to the switch will question the connection and, for security reasons, provide the option of accepting or refusing. If it is safe to assume that an unauthorized device is not using the switch IP address in an attempt to gain access to the client's data or network, the connection can be accepted. (As a more secure alternative, the client can be directly connected to the switch serial port to download the switch public key into the client.)

   NOTE:When an SSH client connects to the switch for the first time, it is possible for a 'man-in-the-middle' attack; that is, for an unauthorized device to pose undetected as the switch, and learn the usernames and passwords controlling access to the switch. This possibility can be removed by directly connecting the management station to the switch serial port, using a show command to display the switch public key, and copying the key from the display into a file. This requires a knowledge of where the client stores public keys, plus the knowledge of what key editing and file format might be required by the client application. However, if the first contact attempt between a client and the switch does not pose a security problem, this is unnecessary.

   Enabling SSH on the switch:

   1. Generate a public/private key pair if you have not already done so. See Generate the switch public and private key pair.

   2. Execute the ip ssh command.

   Disabling SSH on the switch:

   Perform either of the following:

   • Execute no ip ssh.

   • Zeroize the switch existing key pair, see “To generate or erase the switch public/private host key pair:” for more details.

     Syntax:

     Enables or disables SSH on the switch.

     [cipher <cipher-type>]

     Specify a cipher type to use for connection.

     Valid types are:

     • aes128-cbc

     • 3des-cbc

     • aes192-cbc

     • aes256-cbc

     • aes128-ctr

     • aes192-ctr

     • aes256-ctr

     Default: All cipher types are available.

     Use the no form of the command to disable a cipher type.

     Enable/disable secure file transfer capability. SCP and SFTP secure file transfer will not function unless SSH is also enabled.

     [ip-version <4 6 4or6>]

     Select the IP mode to run in. The mode 'ip-version 4' only accepts connections from IPv4 clients. The mode 'ip-version 6' only accepts connections from IPv6 clients. The mode 'ip-version 4or6' accepts connections from both IPv4 and IPv6 clients.

     Default: ip-version 4 or 6

     Allows configuration of the set of MACs that can be selected. Valid types are:

     • hmac-md5

     • hmac-sha1

     • hmac-sha1-96

     • hmac-md5-96

     Default: All MAC types are available.

     Use the no form of the command to disable a MAC type.

     The TCP port number for SSH connections.

     Default: 22.

     Sets the maximum length of time (in seconds) allowed for initial protocol negotiation and authentication.

     Default: 120 seconds

     NOTE:HP recommends using the default TCP port number (22). However, you can use ip ssh port to specify any TCP port for SSH connections except those reserved for other purposes. Examples of reserved port numbers reserved IP ports are 23 (Telnet) and 80 (http). Some other reserved TCP ports on the switch are 49, 80, 1506, and 1513. Apr 11, 2020  Microsoft Office 365 Product Key enables the user to keep the work of his from any component of the earth by using any most recent web browser. There’s no need to put in on all products; the user might continue the work of his using Office internet web apps. Microsoft Office 365 Product Key Generator used for activation of Microsoft Office product full version free. Microsoft Office is the complete product that developed by Microsoft corporation. Microsoft Office 365 Product Key is a complete all-in-one package of tools that support to make office full version to use its all features easily and freely. Ms office 365 activation key generator.

     Enabling IP SSH and displaying the SSH configuration

     CAUTION:Protect your private key file from access by anyone other than yourself. If someone can access your private key file, they can penetrate SSH security on the switch by appearing to be you. SSH does not protect the switch from unauthorized access via the WebAgent, Telnet, SNMP, or the serial port. While WebAgent and Telnet access can be restricted by the use of passwords local to the switch, if you are unsure of the security this provides, you may want to disable web-based and/or Telnet access (no web-management and no Telnet). If you need to increase SNMP security, use SNMP version 3 only. To increase the security of your web interface see the section on SSL. For an additional security measure, see the authorized IP managers feature in the Management and Configuration Guide for your switch. To protect against unauthorized access to the serial port (and the Clear button, which removes local password protection), keep physical access to the switch restricted to authorized personnel.

5. Configure the switch for SSH authentication.

   Note that all methods in this section result in authentication of the switch public key by an SSH client. However only Option B below results in the switch also authenticating the client's public key. Also, for a more detailed discussion of the topics in this section, see SSH client public-key authentication notes.

   NOTE:HP recommends that you always assign a manager-level (enable) password to the switch. Without this level of protection, any user with Telnet, web, or serial port access to the switch can change the switch configuration. If you configure only an operator password, entering the operator password through telnet, web, ssh or serial port access enables full manager privileges. See Assign a local login (operator) and enable (manager) password.

   Option A: Configuring SSH access for password-only SSH authentication:

   When configured with this option, the switch uses its public key to authenticate itself to a client, but uses only passwords for client authentication.

   Syntax:

   aaa authentication ssh login <local tacacs radius>[<local none>]

   Configures a password method for the primary and secondary login (operator) access. If you do not specify an optional secondary method, it defaults to none. If the primary method is local, the secondary method must be none.

   aaa authentication ssh enable <local tacacs radius>[<local none>]

   Configures a password method for the primary and secondary enable (manager) access. If you do not specify an optional secondary method, it defaults to none. If the primary method is local, the secondary method must be none.

   Option B: Configuring the switch for client Public-Key SSH authentication

   If configured with this option, the switch uses its public key to authenticate itself to a client, but the client must also provide a client public key for the switch to authenticate. This option requires the additional step of copying a client public-key file from a TFTP or SFTP server into the switch. This means that before you can use this option, you must:

   1. Create a key pair on an SSH client.

   2. Copy the client's public key into a public-key file (which can contain up to 10 client public keys.)

   3. Copy the public-key file into a TFTP or SFTP server accessible to the switch and download the file to the switch.

   For more on these topics, see SSH client public-key authentication notes.

   With steps a-c complete and SSH properly configured on the switch, if an SSH client contacts the switch, login authentication automatically occurs first, using the switch and client public keys. After the client gains login access, the switch controls client access to the manager level by requiring the passwords configured earlier by the aaa authentication ssh enable command.

   Syntax:

   Copies a public-key file into the switch.

   Configures the switch to authenticate a client public key at the login level with an optional secondary password method.

   Default: none

   Syntax:

   aaa authentication ssh enable <local tacacs radius> <local none>

   Configures a password method for the primary and secondary enable (manager) access. If you do not specify an optional secondary method, it defaults to none.

   If the primary access method is local, you can only specify none for a secondary access method.

   NOTE: The configuration of SSH clients' public keys is stored in flash memory on the switch. You also can save SSH client public-key configurations to a configuration file by entering the following commands: include-credentials write memory For more information about saving security credentials to a configuration file, see Saving security credentials in a config file.

   Example:

   Assume you have a client public-key file named Client-Keys.pub (on a TFTP server at 10.33.18.117) ready for downloading to the switch. For SSH access to the switch allow only clients having a private key that matches a public key found in Client-Keys.pub. For manager-level (enable) access for successful SSH clients use TACACS+ for primary password authentication and local for secondary password authentication, with a manager username of '1eader' and a password of 'm0ns00n'. To set up this operation, configure the switch in a manner similar to the following:

   Configuring for SSH access requiring a client public-key match and manager passwords

   SSH configuration and client public-key listing from figure shows how to check the results of the above commands.

   SSH configuration and client public-key listing from figure

6. Use an SSH client to access the switch.

   Test the SSH configuration on the switch to ensure that you have the level of SSH operation needed for the switch. If you have problems, see 'RADIUS-related problems' in the Management and Configuration Guide for your switch.