Configuring Secure Shell (SSH)
Further Information on SSH Client
1.Use your SSH client application to create a public/private key pair. Refer to the documentation provided with your SSH client application for details. The switch supports the following
Property | Supported | Comments |
| Value |
|
|
|
|
Key Format | ASCII | See figure |
|
| more than one |
|
| with a <CR><LF>. Spaces are allowed within the key to delimit the key’s components. |
|
| Note that, unlike the use of the switch’s public key in an SSH client application, the |
|
| format of a |
|
| address. |
Key Type | RSA only |
|
Maximum Supported | 3072 bits | Shorter key lengths allow faster operation, but also mean diminished security. |
Public Key Length |
|
|
Maximum Key Size | 1024 | Includes the bit size, public index, modulus, any comments, <CR>, <LF>, and all blank |
| characters | spaces. |
|
| If necessary, you can use an editor application to verify the size of a key. For example, |
|
| placing a |
|
| Properties Statistics, lets you view the number of characters in the file, including |
|
| spaces. |
|
|
|
2.Copy the client’s public key into a text file (filename.txt). (For example, you can use the Notepad editor included with the Microsoft® Windows® software. If you want several clients to use client
3.Copy the
Copying a
■One or more
■A copy of each client public key (up to ten) stored in a single text file or individual on a TFTP server to which the switch has access. Terminate all client
Note on Public The actual content of a public key entry in a public key file is determined by
Keysthe SSH client application generating the key. (Although you can manually add or edit any comments the client application adds to the end of the key, such as the smith@fellow at the end of the key in figure