18.08.2013 Views

ClearPath OS 2200 Series Release 13.2 Software Planning and ...

ClearPath OS 2200 Series Release 13.2 Software Planning and ...

ClearPath OS 2200 Series Release 13.2 Software Planning and ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> <strong>Release</strong> 13.1<br />

Cipher API Level 2R2<br />

Compatibility<br />

Cipher API<br />

Cipher API 2R2 is fully compatible with data encrypted by previous levels. The FIPScertified<br />

algorithms used by Cipher API 2R2 are fully compatible with APIs supported in<br />

previous levels, so previously-encrypted data can be safely <strong>and</strong> accurately decrypted<br />

using this level of Cipher API.<br />

Cipher API encryption calls that use dynamic mode will use either hardware or software,<br />

whichever is faster for the specified algorithm, data format, <strong>and</strong> data size. The<br />

CIP2001-PCE encryption card available on the Dorado 800 through I/O Manager has<br />

different latency <strong>and</strong> speed compared with the CIP1001-PCX encryption card attached to<br />

an SIOP or SCIOP on other Dorado servers. Therefore, the ranges in which Cipher API<br />

uses hardware versus software encryption are different for the two cards. To derive<br />

maximum efficiency from Cipher API, the correct configuration file must be loaded. Use<br />

the new installation Mode B for servers having I/O Manager; using this mode<br />

automatically loads the correct configuration file for use with the CIP2001-PCE<br />

encryption card. If no encryption card is installed, the choice of Mode A or Mode B<br />

makes no difference, but by using Mode B on systems such as the Dorado 800 that<br />

support I/O Manager, you are prepared for adding a CIP2001-PCE card later without<br />

having to change the Cipher API configuration file.<br />

Migration<br />

The <strong>OS</strong> <strong>2200</strong> Cryptographic Library (CryptoLib) must be installed for Cipher API to run.<br />

Levels of Cipher API prior to 2R1 did not require CryptoLib.<br />

<strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> <strong>Release</strong> 13.0<br />

Cipher API Level 2R1<br />

Compatibility<br />

Cipher API 2R1 is fully compatible with data encrypted by previous levels. The<br />

FIPS-certified algorithms used by Cipher API 2R1 are fully compatible with the previous<br />

APIs, so previously-encrypted data can be safely <strong>and</strong> accurately decrypted using this<br />

level of Cipher API.<br />

The Initialization Vector (IV) that can be specified on the comm<strong>and</strong> line call in Cipher API<br />

2R1 is optional. Runstreams using the Cipher API 1R3A version of the comm<strong>and</strong> line will<br />

continue to work correctly with Cipher API 2R1.<br />

The new ("level 2") <strong>and</strong> old ("level 1") API calls are supported concurrently. But any<br />

particular program must use only one or the other set of APIs. Users of the new API calls<br />

are cautioned that if they provide their own Initialization Vector, they will not be able to<br />

decrypt the data using the older APIs.<br />

The <strong>OS</strong> <strong>2200</strong> Cryptographic Library (CryptoLib) must be installed for Cipher API 2R1 to<br />

run, even if the level 1 APIs are used.<br />

7831 0349–043 5–3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!