httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mar...@apache.org
Subject cvs commit: httpd-2.0/docs/manual/ssl ssl_faq.html ssl_faq.wml ssl_howto.html ssl_howto.wml ssl_reference.html ssl_reference.wml
Date Mon, 12 Nov 2001 15:08:57 GMT
martin      01/11/12 07:08:57

  Modified:    docs/manual/ssl ssl_faq.html ssl_faq.wml ssl_howto.html
                        ssl_howto.wml ssl_reference.html ssl_reference.wml
  Log:
  It's -> its (where appropriate)
  
  Revision  Changes    Path
  1.3       +3 -3      httpd-2.0/docs/manual/ssl/ssl_faq.html
  
  Index: ssl_faq.html
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/ssl/ssl_faq.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- ssl_faq.html	2001/11/06 19:09:51	1.2
  +++ ssl_faq.html	2001/11/12 15:08:56	1.3
  @@ -292,7 +292,7 @@
   </strong>&nbsp;&nbsp;
       [<a href="http://httpd.apache.org/docs-2.0/ssl/ssl_faq.html#wassenaar"><b>L</b></a>]
       <p>
  -    First, let us explain what <i>Wassenaar</i> and it's <i>Arrangement
on
  +    First, let us explain what <i>Wassenaar</i> and its <i>Arrangement
on
       Export Controls for Conventional Arms and Dual-Use Goods and
       Technologies</i> is: This is a international regime, established 1995, to
       control trade in conventional arms and dual-use goods and technology. It
  @@ -504,7 +504,7 @@
       <code><b>$ telnet localhost 80</b></code><br>
       <code><b>GET / HTTP/1.0</b></code>
       <p>
  -    for simple testing the HTTP protocol of Apache, it's not such easy for
  +    for simple testing the HTTP protocol of Apache, it's not so easy for
       HTTPS because of the SSL protocol between TCP and HTTP. But with the
       help of OpenSSL's <code>s_client</code> command you can do a similar
       check even for HTTPS:
  @@ -1379,4 +1379,4 @@
   
   <p><!--#include virtual="footer.html" --> </p>
     </body>
  -</html>
  \ No newline at end of file
  +</html>
  
  
  
  1.2       +2 -2      httpd-2.0/docs/manual/ssl/ssl_faq.wml
  
  Index: ssl_faq.wml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/ssl/ssl_faq.wml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- ssl_faq.wml	2001/11/05 17:43:12	1.1
  +++ ssl_faq.wml	2001/11/12 15:08:56	1.2
  @@ -231,7 +231,7 @@
   What about mod_ssl and the Wassenaar Arrangement?
   </faq>
   
  -    First, let us explain what <i>Wassenaar</i> and it's <i>Arrangement
on
  +    First, let us explain what <i>Wassenaar</i> and its <i>Arrangement
on
       Export Controls for Conventional Arms and Dual-Use Goods and
       Technologies</i> is: This is a international regime, established 1995, to
       control trade in conventional arms and dual-use goods and technology. It
  @@ -424,7 +424,7 @@
       <code><b>$ telnet localhost 80</b></code><br>
       <code><b>GET / HTTP/1.0</b></code>
       <p>
  -    for simple testing the HTTP protocol of Apache, it's not such easy for
  +    for simple testing the HTTP protocol of Apache, it's not so easy for
       HTTPS because of the SSL protocol between TCP and HTTP. But with the
       help of OpenSSL's <code>s_client</code> command you can do a similar
       check even for HTTPS:
  
  
  
  1.3       +3 -3      httpd-2.0/docs/manual/ssl/ssl_howto.html
  
  Index: ssl_howto.html
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/ssl/ssl_howto.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- ssl_howto.html	2001/11/06 19:09:51	1.2
  +++ ssl_howto.html	2001/11/12 15:08:56	1.3
  @@ -45,7 +45,7 @@
   way of processing requests. This chapter gives instructions on how to solve
   such typical situations. Treat is as a first step to find out the final
   solution, but always try to understand the stuff before you use it. Nothing is
  -worse than using a security solution without knowing it's restrictions and
  +worse than using a security solution without knowing its restrictions and
   coherences.
   
   <ul>
  @@ -174,7 +174,7 @@
   In short: The server has a Global ID server certificate, signed by a special
   CA certificate from Verisign which enables strong encryption in export
   browsers. This works as following: The browser connects with an export cipher,
  -the server sends it's Global ID certificate, the browser verifies it and
  +the server sends its Global ID certificate, the browser verifies it and
   subsequently upgrades the cipher suite before any HTTP communication takes
   place. The question now is: How can we allow this upgrade, but enforce strong
   encryption. Or in other words: Browser either have to initially connect with
  @@ -652,4 +652,4 @@
   
   <p><!--#include virtual="footer.html" --> </p>
     </body>
  -</html>
  \ No newline at end of file
  +</html>
  
  
  
  1.2       +2 -2      httpd-2.0/docs/manual/ssl/ssl_howto.wml
  
  Index: ssl_howto.wml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/ssl/ssl_howto.wml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- ssl_howto.wml	2001/11/05 17:43:12	1.1
  +++ ssl_howto.wml	2001/11/12 15:08:56	1.2
  @@ -21,7 +21,7 @@
   way of processing requests. This chapter gives instructions on how to solve
   such typical situations. Treat is as a first step to find out the final
   solution, but always try to understand the stuff before you use it. Nothing is
  -worse than using a security solution without knowing it's restrictions and
  +worse than using a security solution without knowing its restrictions and
   coherences.
   
   </td>
  @@ -121,7 +121,7 @@
   In short: The server has a Global ID server certificate, signed by a special
   CA certificate from Verisign which enables strong encryption in export
   browsers. This works as following: The browser connects with an export cipher,
  -the server sends it's Global ID certificate, the browser verifies it and
  +the server sends its Global ID certificate, the browser verifies it and
   subsequently upgrades the cipher suite before any HTTP communication takes
   place. The question now is: How can we allow this upgrade, but enforce strong
   encryption. Or in other words: Browser either have to initially connect with
  
  
  
  1.2       +3 -3      httpd-2.0/docs/manual/ssl/ssl_reference.html
  
  Index: ssl_reference.html
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/ssl/ssl_reference.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- ssl_reference.html	2001/11/05 17:42:41	1.1
  +++ ssl_reference.html	2001/11/12 15:08:56	1.2
  @@ -600,7 +600,7 @@
   The following <em>source</em> variants are available:
   <ul>
   <li><code>builtin</code>
  -    <p> This is the always available builtin seeding source. It's usage
  +    <p> This is the always available builtin seeding source. Its usage
       consumes minimum CPU cycles under runtime and hence can be always used
       without drawbacks. The source used for seeding the PRNG contains of the
       current time, the current process id and (when applicable) a randomly
  @@ -638,7 +638,7 @@
       find under <i>rndcontrol(8)</i> on those platforms. Alternatively, when
       your system lacks such a random device, you can use tool
       like <a href="http://www.lothar.com/tech/crypto/">EGD</a>
  -    (Entropy Gathering Daemon) and run it's client program with the
  +    (Entropy Gathering Daemon) and run its client program with the
       <code>exec:/path/to/program/</code> variant (see below) or use
       <code>egd:/path/to/egd-socket</code> (see below).
   <p>
  @@ -974,7 +974,7 @@
       This is the Transport Layer Security (TLS) protocol, version 1.0. It is the
       successor to SSLv3 and currently (as of February 1999) still under
       construction by the Internet Engineering Task Force (IETF). It's still
  -    not supported by any popular browsers.
  +    not supported by all popular browsers.
   <p>
   <li><code>All</code>
       <p>
  
  
  
  1.2       +3 -3      httpd-2.0/docs/manual/ssl/ssl_reference.wml
  
  Index: ssl_reference.wml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/ssl/ssl_reference.wml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- ssl_reference.wml	2001/11/05 17:43:12	1.1
  +++ ssl_reference.wml	2001/11/12 15:08:57	1.2
  @@ -259,7 +259,7 @@
   
   <ul>
   <li><code>builtin</code>
  -    <p> This is the always available builtin seeding source.  It's usage
  +    <p> This is the always available builtin seeding source.  Its usage
       consumes minimum CPU cycles under runtime and hence can be always used
       without drawbacks. The source used for seeding the PRNG contains of the
       current time, the current process id and (when applicable) a randomly
  @@ -297,7 +297,7 @@
       find under <i>rndcontrol(8)</i> on those platforms.  Alternatively, when
       your system lacks such a random device, you can use tool
       like <a href="http://www.lothar.com/tech/crypto/">EGD</a>
  -    (Entropy Gathering Daemon) and run it's client program with the
  +    (Entropy Gathering Daemon) and run its client program with the
       <code>exec:/path/to/program/</code> variant (see below) or use
       <code>egd:/path/to/egd-socket</code> (see below).
   <p>
  @@ -513,7 +513,7 @@
       This is the Transport Layer Security (TLS) protocol, version 1.0.  It is the
       successor to SSLv3 and currently (as of February 1999) still under
       construction by the Internet Engineering Task Force (IETF).  It's still
  -    not supported by any popular browsers.
  +    not supported by all popular browsers.
   <p>
   <li><code>All</code>
       <p>
  
  
  

Mime
View raw message