67 lines
4.6 KiB
HTML
67 lines
4.6 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="IBM Cryptographic Coprocessors for iSeries" />
|
|
<meta name="abstract" content="The cryptographic coprocessor provides proven cryptographic services, ensuring privacy and integrity, for developing secure e-business applications." />
|
|
<meta name="description" content="The cryptographic coprocessor provides proven cryptographic services, ensuring privacy and integrity, for developing secure e-business applications." />
|
|
<meta name="DC.Relation" scheme="URI" content="rzahurzahu4abunderstanddc.htm" />
|
|
<meta name="DC.Relation" scheme="URI" content="rzahurzahucrp1createcertonhw.htm" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2000, 2006" />
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2000, 2006" />
|
|
<meta name="DC.Format" content="XHTML" />
|
|
<meta name="DC.Identifier" content="crypto_card_concept" />
|
|
<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>IBM Cryptographic
|
|
Coprocessors for iSeries</title>
|
|
</head>
|
|
<body id="crypto_card_concept"><a name="crypto_card_concept"><!-- --></a>
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|
<h1 class="topictitle1">IBM Cryptographic
|
|
Coprocessors for <span class="keyword">iSeries</span></h1>
|
|
<div><p>The cryptographic coprocessor provides proven cryptographic services,
|
|
ensuring privacy and integrity, for developing secure e-business applications. </p>
|
|
<p>Using an IBM<sup>®</sup> Cryptographic Coprocessor for <span class="keyword">iSeries™</span> adds
|
|
highly secure cryptographic processing capability to your system. If you have
|
|
a cryptographic coprocessor installed and varied on for your system, you can
|
|
use the cryptographic coprocessor to provide more secure key storage for your
|
|
certificate private keys. </p>
|
|
<p>You can use the cryptographic coprocessor to store the private key for
|
|
a server or client certificate and for a local Certificate Authority (CA)
|
|
certificate. However, you cannot use the cryptographic coprocessor to store
|
|
a user certificate private key because this key must be stored on the user's
|
|
system. Also, you cannot use the coprocessor to store the private key for
|
|
an object signing certificate at this time. </p>
|
|
<p>You can either store a certificate private key directly in the cryptographic
|
|
coprocessor, or you can use the cryptographic coprocessor master key to encrypt
|
|
the key and store it in a special key file. You can select these key storage
|
|
options as part of the process of creating or renewing a certificate. Also,
|
|
if you use the coprocessor to store a certificate's private key, you can change
|
|
the coprocessor device assignment for that key. </p>
|
|
<p>To use the cryptographic coprocessor for private key storage, you must
|
|
ensure that the coprocessor is varied on before using Digital Certificate
|
|
Manager (DCM). Otherwise, DCM does not provide the option for selecting a
|
|
storage location as part of the certificate creation or renewal process. </p>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzahurzahu4abunderstanddc.htm" title="View this information to better understand what digital certificates are and how they work. Learn about the different types of certificates and how you can use them as part of your security policy.">DCM concepts</a></div>
|
|
</div>
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
|
<div><a href="rzahurzahucrp1createcertonhw.htm" title="Review this information to learn how to use an installed coprocessor to provide more secure storage for your certificates' private keys.">Store certificate keys on an IBM Cryptographic Coprocessor</a></div>
|
|
</div>
|
|
</div>
|
|
</body>
|
|
</html> |