Configuring Secure Shell (SSH)
Further Information on SSH Client Public-Key Authentication
N o t e s
Comments in public key files, such as
in figure 7-13,
may appear in a SSH client application’s generated public key. While such
comments may help to distinguish one key from another, they do not pose any
restriction on the use of a key by multiple clients and/or users.
Public key illustrations such as the key shown in figure 7-13 usually include
line breaks as a method for showing the whole key. However, in practice, line
breaks in a public key will cause errors resulting in authentication failure.
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 client-public-key properties:
Property
Supported
Value
Comments
Key Format
ASCII
See figure 7-7 on page 7-13. The key must be one unbroken ASCII string. If you add
more than one client-public-key to a file, terminate each key (except the last 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 client-public-key used by the switch does not include the client’s IP
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
characters
Includes the bit size, public index, modulus, any comments, <CR>, <LF>, and all blank
spaces.
If necessary, you can use an editor application to verify the size of a key. For example,
placing a client-public-key into a Word for Windows text file and clicking on
File |
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 public-key authentica
tion, copy a public key for each of these clients (up to ten) into the file.
Each key should be separated from the preceding key by a <CR><LF>.
3.
Copy the client-public-key file into a TFTP server accessible to the switch.
Copying a client-public-key into the switch requires the following:
■
One or more client-generated public keys. Refer to the documentation
provided with your SSH client application.
■
A copy of each client public key (up to ten) stored in a single text file
or individually on a TFTP server to which the switch has access.
Terminate all client public-keys in the file except the last one with a
<CR><LF>.
7-24
Содержание J8697A
Страница 1: ...6200yl Access Security Guide 5400zl 3500yl ProCurve Switches K 11 XX www procurve com ...
Страница 2: ......
Страница 22: ...Product Documentation Feature Index xx ...
Страница 55: ...Configuring Username and Password Security Front Panel Security 2 21 ...
Страница 56: ...Configuring Username and Password Security Front Panel Security 2 22 ...
Страница 58: ...Virus Throttling Contents Operating Notes 3 30 Connection Rate Log and Trap Messages 3 31 3 2 ...
Страница 88: ...Virus Throttling Connection Rate Log and Trap Messages This page is intentionally unused 3 32 ...
Страница 118: ...Web and MAC Authentication Client Status This page intentionally unused 4 30 ...
Страница 230: ...Configuring Secure Socket Layer SSL Common Errors in SSL setup This page is intentionally unused 8 22 ...
Страница 356: ...Configuring and Monitoring Port Security Operating Notes for Port Security 11 44 ...
Страница 370: ...Using Authorized IP Managers Operating Notes This page is intentionally unused 12 14 ...
Страница 388: ...10 Index ...
Страница 389: ......