69 lines
4.5 KiB
HTML
69 lines
4.5 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="Name files to key store file" />
|
||
|
|
<meta name="abstract" content="Before you can perform any operation using a key store file or key stored in a key store file, you must name the key store file." />
|
||
|
|
<meta name="description" content="Before you can perform any operation using a key store file or key stored in a key store file, you must name the key store file." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajcsetup.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="namefiles" />
|
||
|
|
<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>Name files to key store file</title>
|
||
|
|
</head>
|
||
|
|
<body id="namefiles"><a name="namefiles"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Name files to key store file</h1>
|
||
|
|
<div><p>Before you can perform any operation using a key store file or
|
||
|
|
key stored in a key store file, you must name the key store file. </p>
|
||
|
|
<p>You can name two types of key store files. One type stores Data Encryption
|
||
|
|
Standard (DES) keys and Triple-DES keys. DES and Triple DES are symmetric
|
||
|
|
cryptographic algorithms; the Cryptographic Coprocessor uses the same key
|
||
|
|
to encrypt and decrypt. The other type stores public key algorithm (PKA) keys.
|
||
|
|
Public key algorithms are asymmetric; keys are created in pairs. Cryptographic
|
||
|
|
Coprocessors use one key to encrypt and the other to decrypt. Cryptographic
|
||
|
|
Coprocessors support the RSA public key algorithm.</p>
|
||
|
|
<p>You can name a key store file explicitly by using a program, or you can
|
||
|
|
name it by configuring it on the device description. To name a key store file
|
||
|
|
from a program, use the Key_Store_Designate (CSUKSD) security application
|
||
|
|
programming interface (SAPI). If you name key store files that use a program,
|
||
|
|
your Cryptographic Coprocessor only uses the names for the job that ran the
|
||
|
|
program. However, by naming key store files explicitly in your program, you
|
||
|
|
can use separate key store files from other users. If you name key store files
|
||
|
|
on the device description, you do not have to name them in your program. This
|
||
|
|
may help if you are trying to maintain the same program source across multiple IBM<sup>®</sup> platforms.
|
||
|
|
It is also useful if you are porting a program from another implementation
|
||
|
|
of Common Cryptographic Architecture. </p>
|
||
|
|
<p>You need to store your cryptographic keys in a secure form so that you
|
||
|
|
can use them over time and exchange them with other users and servers, as
|
||
|
|
appropriate. You can store your cryptographic keys by using your own methods,
|
||
|
|
or you can store them in a key store file. You can have as many key store
|
||
|
|
files as you want, and you can create multiple key store files for each type
|
||
|
|
of key. You can place as many cryptographic keys in your key store files as
|
||
|
|
you want.</p>
|
||
|
|
<p>Since each key store file is a separate server object, you can authorize
|
||
|
|
different users to each file. You can save and restore each key store file
|
||
|
|
at different times. This depends on how often the file's data changes or which
|
||
|
|
data it is protecting.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajcsetup.htm" title="Configuring your Cryptographic Coprocessor allows you to begin to use all of its cryptographic operations.">Configure the Cryptographic Coprocessor</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|