![IBM WebSphere XS40 Скачать руководство пользователя страница 247](http://html.mh-extra.com/html/ibm/websphere-xs40/websphere-xs40_command-reference-manual_607316247.webp)
v
Deletes the
FWCred-1
Firewall Credentials.
# no fwcred FWCred-1
Firewall Credentials 'FWCred-1' deleted
#
hsm-clone-kwk (HSM models)
Clones a key wrapping key between HSM-equipped appliances.
Syntax
hsm-clone-kwk
[
input
filename
] [
output
filename
]
Parameters
input
filename
Indicates the name of the local file to use as input to the cloning action.
During the first part of this four-part task, do not specify this parameter.
During the other parts of this task, this parameter is required.
output
filename
Indicates the name of the local file that the cloning action creates. During
the last part of this four-part task, do not specify this parameter. During
the other parts of this task, this parameter is required.
Guidelines
This command is available only on systems with an internal HSM.
Use the
hsm-clone-kwk
command if two HSM-equipped systems share the same
red (hardware) key and if both systems are at the same FIPS security level. This
command copies the key-wrapping key from the source HSM system to the
destination HSM system. You must run this command four times.
1.
On the source HSM system, create an output file (for example,
temporary:///source-one
that contains the key material. After validating that
the command created the file, copy it to the destination HSM system.
2.
On the destination HSM system, create an output file (for example,
temporary:///destination-two
that uses the copied file (for example,
temporary:///source-one
) as the input file. After validating that the command
created the file, copy it to the source HSM system.
3.
On the source HSM system, create an output file (for example,
temporary:///source-three
that uses the copied file (for example,
temporary:///destination-two
) as the input file. After validating that the
command created the file, copy it to the destination HSM system.
4.
On the destination HSM system, use the copied file (for example,
temporary:///source-three
) as the input file.
At this point, the source and destination HSM systems share the same
key-wrapping key. After cloning the key-wrapping key on each HSM domain
member, the domain member can share keys in the following way:
1.
Creating an export crypto object
2.
Transferring the export crypto object to a target system in the HSM domain
3.
Importing the export crypto object on the target system
Refer to the HSM documentation for information about performing the key cloning
task from the WebGUI.
Chapter 11. Crypto configuration mode
221
Содержание WebSphere XS40
Страница 1: ...WebSphere DataPower XML Security Gateway XS40 Command Reference Version 3 7 2 ...
Страница 2: ......
Страница 3: ...WebSphere DataPower XML Security Gateway XS40 Command Reference Version 3 7 2 ...
Страница 44: ...18 Command Reference ...
Страница 194: ...168 Command Reference ...
Страница 198: ...172 Command Reference ...
Страница 206: ...180 Command Reference ...
Страница 210: ...184 Command Reference ...
Страница 222: ...196 Command Reference ...
Страница 232: ...206 Command Reference ...
Страница 238: ...212 Command Reference ...
Страница 268: ...242 Command Reference ...
Страница 272: ...246 Command Reference ...
Страница 276: ...250 Command Reference ...
Страница 288: ...262 Command Reference ...
Страница 292: ...266 Command Reference ...
Страница 298: ...272 Command Reference ...
Страница 320: ...294 Command Reference ...
Страница 322: ...296 Command Reference ...
Страница 340: ...314 Command Reference ...
Страница 344: ...318 Command Reference ...
Страница 352: ...326 Command Reference ...
Страница 360: ...334 Command Reference ...
Страница 368: ...342 Command Reference ...
Страница 376: ...350 Command Reference ...
Страница 386: ...360 Command Reference ...
Страница 392: ...366 Command Reference ...
Страница 396: ...370 Command Reference ...
Страница 402: ...376 Command Reference ...
Страница 404: ...378 Command Reference ...
Страница 408: ...382 Command Reference ...
Страница 446: ...420 Command Reference ...
Страница 450: ...424 Command Reference ...
Страница 456: ...430 Command Reference ...
Страница 458: ... message type Extranet Message type configuration mode no message matching TFDef2 432 Command Reference ...
Страница 520: ...494 Command Reference ...
Страница 536: ...510 Command Reference ...
Страница 550: ...524 Command Reference ...
Страница 584: ...558 Command Reference ...
Страница 600: ...574 Command Reference ...
Страница 605: ... timeout 500 Chapter 63 RADIUS configuration mode 579 ...
Страница 606: ...580 Command Reference ...
Страница 638: ...v Allow access by the admin account to all access methods restrict admin off 612 Command Reference ...
Страница 650: ...624 Command Reference ...
Страница 667: ...v Specifies support for SNMP Version 2c the default state version 2c Chapter 72 SNMP Settings configuration mode 641 ...
Страница 668: ...642 Command Reference ...
Страница 704: ...678 Command Reference ...
Страница 714: ...688 Command Reference ...
Страница 726: ...700 Command Reference ...
Страница 734: ...708 Command Reference ...
Страница 752: ...726 Command Reference ...
Страница 756: ...730 Command Reference ...
Страница 804: ...778 Command Reference ...
Страница 880: ...854 Command Reference ...
Страница 892: ...866 Command Reference ...
Страница 912: ...886 Command Reference ...
Страница 918: ...892 Command Reference ...
Страница 940: ...914 Command Reference ...
Страница 946: ...920 Command Reference ...
Страница 974: ...948 Command Reference ...
Страница 1004: ...978 Command Reference ...
Страница 1030: ...1004 Command Reference ...
Страница 1032: ...1006 Command Reference ...
Страница 1038: ...Other company product and service names may be trademarks or service marks of others 1012 Command Reference ...
Страница 1065: ......
Страница 1066: ... Printed in USA ...