61 lines
4.1 KiB
HTML
61 lines
4.1 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="Public-private key pair" />
|
||
|
|
<meta name="abstract" content="Every digital certificate has a pair of associated cryptographic keys that consist of a private key and a public key." />
|
||
|
|
<meta name="description" content="Every digital certificate has a pair of associated cryptographic keys that consist of a private key and a public key." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahurzahu4abunderstanddc.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahudigsig.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzahurzahu02mcertificateauthority.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="keypair" />
|
||
|
|
<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>Public-private key pair</title>
|
||
|
|
</head>
|
||
|
|
<body id="keypair"><a name="keypair"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Public-private key pair</h1>
|
||
|
|
<div><p>Every digital certificate has a pair of associated cryptographic
|
||
|
|
keys that consist of a private key and a public key. </p>
|
||
|
|
<div class="p"><div class="note"><span class="notetitle">Note:</span> Signature verification certificates are an exception
|
||
|
|
to this rule and have an associated public key only.</div>
|
||
|
|
A public key is
|
||
|
|
part of the owner's digital certificate and is available for anyone to use.
|
||
|
|
A private key, however, is protected by and available only to the owner of
|
||
|
|
the key. This limited access ensures that communications that use the key
|
||
|
|
are kept secure.</div>
|
||
|
|
<p>The owner of a certificate can use these keys to take advantage of the
|
||
|
|
cryptographic security features that the keys provide. For example, the certificate
|
||
|
|
owner can use a certificate's private key to "sign" and encrypt data sent
|
||
|
|
between users and servers, such as messages, documents, and code objects.
|
||
|
|
The recipient of the signed object can then use the public key contained in
|
||
|
|
the signer's certificate to decrypt the signature. Such digital signatures
|
||
|
|
ensure the reliability of an object's origin and provide a means of checking
|
||
|
|
the integrity of the object.</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="rzahudigsig.htm" title="A digital signature on an electronic document or other object is created by using a form of cryptography and is equivalent to a personal signature on a written document.">Digital signatures</a></div>
|
||
|
|
<div><a href="rzahurzahu02mcertificateauthority.htm" title="A Certificate Authority (CA) is a trusted central administrative entity that can issue digital certificates to users and servers.">Certificate Authority (CA)</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|