httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j..@apache.org
Subject cvs commit: httpd-2.0/docs/manual glossary.html.en glossary.xml
Date Sat, 11 Oct 2003 05:20:47 GMT
jsl         2003/10/10 22:20:47

  Modified:    docs/manual glossary.html.en glossary.xml
  Log:
  a href updates, plus transformation.
  
  Revision  Changes    Path
  1.15      +14 -13    httpd-2.0/docs/manual/glossary.html.en
  
  Index: glossary.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/glossary.html.en,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- glossary.html.en	29 May 2003 16:12:27 -0000	1.14
  +++ glossary.html.en	11 Oct 2003 05:20:47 -0000	1.15
  @@ -53,10 +53,10 @@
   <dt><a name="certificate">Certificate</a></dt>
   <dd>A data record used for authenticating network entities such
       as a server or a client. A certificate contains X.509 information pieces
  -    about its owner (called the subject) and the signing <em>Certificate
  -    Authority</em> (called the issuer), plus the owner's public key and the
  -    signature made by the CA. Network entities verify these signatures using
  -    CA certificates.<br />
  +    about its owner (called the subject) and the signing <a href="#certificationauthority">Certification
Authority</a> (called the
  +    issuer), plus the owner's <a href="#publickey">public key</a> and the
  +    signature made by the CA. Network entities verify these signatures
  +    using CA certificates.<br />
   See: <a href="ssl/">SSL/TLS Encryption</a></dd>
   
   <dt><a name="certificationauthority">Certification Authority</a> <a
name="ca">(CA)</a></dt> <dd>A trusted third party whose purpose is to
  @@ -66,10 +66,10 @@
   See: <a href="ssl/">SSL/TLS Encryption</a></dd>
   
   <dt><a name="certificatsigningrequest">Certificate Signing Request</a>
  -<a name="csr">(CSR)</a></dt> <dd>An unsigned certificate for
  -submission to a <em>Certification Authority</em>, which signs it with
  -the <em>Private Key</em> of their CA <em>Certificate</em>. Once
the
  -CSR is signed, it becomes a real certificate.<br />
  +<a name="csr">(CSR)</a></dt> <dd>An unsigned <a href="#certificate">certificate</a>
for submission to a <a href="#certificationauthority">Certification Authority</a>,
which signs it
  +with the <a href="#privatekey">Private Key</a> of their CA
  +<em>Certificate</em>. Once the CSR is signed, it becomes a real
  +certificate.<br />
   See: <a href="ssl/">SSL/TLS Encryption</a></dd>
   
   
  @@ -107,11 +107,12 @@
   
   <dt><a name="digitalsignature">Digital Signature</a></dt>
   <dd>An encrypted text block that validates a certificate or other file. A
  -    <em>Certification Authority</em> creates a signature by generating a
  -    hash of the <em>Public Key</em> embedded in a <em>Certificate</em>,
then
  -    encrypting the hash with its own <em>Private Key</em>. Only the CA's
  -    public key can decrypt the signature, verifying that the CA has
  -    authenticated the network entity that owns the <em>Certificate</em>.<br
/>
  +    <a href="#certificationauthority">Certification Authority</a> creates a
  +    signature by generating a hash of the <em>Public Key</em> embedded in a
  +    <em>Certificate</em>, then encrypting the hash with its own <em>Private
  +    Key</em>. Only the CA's public key can decrypt the signature, verifying
  +    that the CA has authenticated the network entity that owns the
  +    <em>Certificate</em>.<br />
   See: <a href="ssl/">SSL/TLS Encryption</a></dd>
   
   <dt><a name="directive">Directive</a></dt> <dd>A configuration
command
  
  
  
  1.9       +17 -13    httpd-2.0/docs/manual/glossary.xml
  
  Index: glossary.xml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/glossary.xml,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- glossary.xml	12 Apr 2003 15:04:43 -0000	1.8
  +++ glossary.xml	11 Oct 2003 05:20:47 -0000	1.9
  @@ -43,10 +43,11 @@
   <dt><a name="certificate">Certificate</a></dt>
   <dd>A data record used for authenticating network entities such
       as a server or a client. A certificate contains X.509 information pieces
  -    about its owner (called the subject) and the signing <em>Certificate
  -    Authority</em> (called the issuer), plus the owner's public key and the
  -    signature made by the CA. Network entities verify these signatures using
  -    CA certificates.<br />
  +    about its owner (called the subject) and the signing <a
  +    href="#certificationauthority">Certification Authority</a> (called the
  +    issuer), plus the owner's <a href="#publickey">public key</a> and the
  +    signature made by the CA. Network entities verify these signatures
  +    using CA certificates.<br />
   See: <a href="ssl/">SSL/TLS Encryption</a></dd>
   
   <dt><a name="certificationauthority">Certification Authority</a> <a
  @@ -57,10 +58,12 @@
   See: <a href="ssl/">SSL/TLS Encryption</a></dd>
   
   <dt><a name="certificatsigningrequest">Certificate Signing Request</a>
  -<a name="csr">(CSR)</a></dt> <dd>An unsigned certificate for
  -submission to a <em>Certification Authority</em>, which signs it with
  -the <em>Private Key</em> of their CA <em>Certificate</em>. Once
the
  -CSR is signed, it becomes a real certificate.<br />
  +<a name="csr">(CSR)</a></dt> <dd>An unsigned <a
  +href="#certificate">certificate</a> for submission to a <a
  +href="#certificationauthority">Certification Authority</a>, which signs it
  +with the <a href="#privatekey">Private Key</a> of their CA
  +<em>Certificate</em>. Once the CSR is signed, it becomes a real
  +certificate.<br />
   See: <a href="ssl/">SSL/TLS Encryption</a></dd>
   
   
  @@ -104,11 +107,12 @@
   
   <dt><a name="digitalsignature">Digital Signature</a></dt>
   <dd>An encrypted text block that validates a certificate or other file. A
  -    <em>Certification Authority</em> creates a signature by generating a
  -    hash of the <em>Public Key</em> embedded in a <em>Certificate</em>,
then
  -    encrypting the hash with its own <em>Private Key</em>. Only the CA's
  -    public key can decrypt the signature, verifying that the CA has
  -    authenticated the network entity that owns the <em>Certificate</em>.<br
/>
  +    <a href="#certificationauthority">Certification Authority</a> creates a
  +    signature by generating a hash of the <em>Public Key</em> embedded in a
  +    <em>Certificate</em>, then encrypting the hash with its own <em>Private
  +    Key</em>. Only the CA's public key can decrypt the signature, verifying
  +    that the CA has authenticated the network entity that owns the
  +    <em>Certificate</em>.<br />
   See: <a href="ssl/">SSL/TLS Encryption</a></dd>
   
   <dt><a name="directive">Directive</a></dt> <dd>A configuration
command
  
  
  

Mime
View raw message