74 lines
5.2 KiB
HTML
74 lines
5.2 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="concept" />
|
||
|
|
<meta name="DC.Title" content="Initialize a key store file" />
|
||
|
|
<meta name="abstract" content="A key store file is a database file that stores operational keys, i.e. keys encrypted under the master key. Read this information if you plan to keep records of your DES and PKA keys." />
|
||
|
|
<meta name="description" content="A key store file is a database file that stores operational keys, i.e. keys encrypted under the master key. Read this information if you plan to keep records of your DES and PKA keys." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajcworking.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajcinzpkeystc.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajcinzpkeystrpg.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajcconcepts.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajccreatekeys.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="initialstore" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Initialize a key store file</title>
|
||
|
|
</head>
|
||
|
|
<body id="initialstore"><a name="initialstore"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Initialize a key store file</h1>
|
||
|
|
<div><p>A key store file is a database file that stores operational keys,
|
||
|
|
i.e. keys encrypted under the master key. Read this information if you plan
|
||
|
|
to keep records of your DES and PKA keys.</p>
|
||
|
|
<p> You can initialize two different types of key stores for your Cryptographic
|
||
|
|
Coprocessor. The Cryptographic Coprocessor uses one type to store PKA keys
|
||
|
|
and the other to store DES keys. You need to initialize a key store file if
|
||
|
|
you plan to store keys in it. Even though retain keys are not stored in a
|
||
|
|
key store file, one is still required because CCA searches for labels in key
|
||
|
|
store files before it searches for labels in the coprocessor.</p>
|
||
|
|
<p>The CCA CSP creates a DB2<sup>®</sup> key store file, if one does not already exist. If
|
||
|
|
a key store file already exists, the CCA CSP deletes the file and recreates
|
||
|
|
a new one.</p>
|
||
|
|
<p>To initialize a key store, you can use the Cryptographic Coprocessor configuration
|
||
|
|
utility. Click on <span class="uicontrol">Manage configuration</span> and then click
|
||
|
|
on either <span class="uicontrol">DES keys</span> or <span class="uicontrol">PKA keys</span> depending
|
||
|
|
upon what key store file you wish to initialize. With the utility, you can
|
||
|
|
only initialize a file if it does not already exist.</p>
|
||
|
|
<p>If you would rather write your own application to initialize a key store
|
||
|
|
file, you can do so by using the KeyStore_Initialize (CSNBKSI) API verb. </p>
|
||
|
|
<p>After you create a key store for your Cryptographic Coprocessor, you can
|
||
|
|
generate DES and PKA keys to store in your key store files.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ul class="ullinks">
|
||
|
|
<li class="ulchildlink"><strong><a href="rzajcinzpkeystc.htm">Example: ILE C program for initializing a key store for your Cryptographic Coprocessor</a></strong><br />
|
||
|
|
Change this program example to suit your needs for initializing a key store for your Cryptographic Coprocessor.</li>
|
||
|
|
<li class="ulchildlink"><strong><a href="rzajcinzpkeystrpg.htm">Example: ILE RPG program for initializing a key store for your Cryptographic Coprocessor</a></strong><br />
|
||
|
|
Change this program example to suit your needs for initializing a key store for your Cryptographic Coprocessor.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajcworking.htm" title="After you set up your Cryptographic Coprocessor, you can begin writing programs to make use of your Cryptographic Coprocessor's cryptographic functions.">Manage the Cryptographic Coprocessor</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzajcconcepts.htm" title="This article provides a basic understanding of cryptographic function and an overview of the server's cryptographic services">Cryptography concepts</a></div>
|
||
|
|
<div><a href="rzajccreatekeys.htm" title="You can create DES and PKA keys and store them in a DES key store.">Create DES and PKA keys</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|