From 7fc3e6247406f0c2e2be950b7464082d046b5f85 Mon Sep 17 00:00:00 2001 From: Martin Kraemer Date: Mon, 12 Nov 2001 15:08:57 +0000 Subject: [PATCH] It's -> its (where appropriate) git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@91874 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/ssl/ssl_faq.html | 6 +++--- docs/manual/ssl/ssl_faq.wml | 4 ++-- docs/manual/ssl/ssl_howto.html | 6 +++--- docs/manual/ssl/ssl_howto.wml | 4 ++-- docs/manual/ssl/ssl_reference.html | 6 +++--- docs/manual/ssl/ssl_reference.wml | 6 +++--- 6 files changed, 16 insertions(+), 16 deletions(-) diff --git a/docs/manual/ssl/ssl_faq.html b/docs/manual/ssl/ssl_faq.html index 8cb10bb816..e7ea61f0ba 100644 --- a/docs/manual/ssl/ssl_faq.html +++ b/docs/manual/ssl/ssl_faq.html @@ -292,7 +292,7 @@ What about mod_ssl and the Wassenaar Arrangement?    [L]

- First, let us explain what Wassenaar and it's Arrangement on + First, let us explain what Wassenaar and its Arrangement on Export Controls for Conventional Arms and Dual-Use Goods and Technologies 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 @@ How can I speak HTTPS manually for testing purposes? $ telnet localhost 80
GET / HTTP/1.0

- 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 s_client command you can do a similar check even for HTTPS: @@ -1379,4 +1379,4 @@ Follow the following steps:

- \ No newline at end of file + diff --git a/docs/manual/ssl/ssl_faq.wml b/docs/manual/ssl/ssl_faq.wml index b6ab234b26..0b0b2e3b84 100644 --- a/docs/manual/ssl/ssl_faq.wml +++ b/docs/manual/ssl/ssl_faq.wml @@ -231,7 +231,7 @@ Is mod_ssl Year 2000 compliant? What about mod_ssl and the Wassenaar Arrangement? - First, let us explain what Wassenaar and it's Arrangement on + First, let us explain what Wassenaar and its Arrangement on Export Controls for Conventional Arms and Dual-Use Goods and Technologies 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 @@ How can I speak HTTPS manually for testing purposes? $ telnet localhost 80
GET / HTTP/1.0

- 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 s_client command you can do a similar check even for HTTPS: diff --git a/docs/manual/ssl/ssl_howto.html b/docs/manual/ssl/ssl_howto.html index dfbc963278..9f00fe3920 100644 --- a/docs/manual/ssl/ssl_howto.html +++ b/docs/manual/ssl/ssl_howto.html @@ -45,7 +45,7 @@ is not always obvious because of the coherences between SSL, HTTP and Apache's 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.

    @@ -174,7 +174,7 @@ find in the README.GlobalID document in the mod_ssl distribution. 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 @@ Require valid-user

    - \ No newline at end of file + diff --git a/docs/manual/ssl/ssl_howto.wml b/docs/manual/ssl/ssl_howto.wml index 7ce00b04d0..0ce6dfcc76 100644 --- a/docs/manual/ssl/ssl_howto.wml +++ b/docs/manual/ssl/ssl_howto.wml @@ -21,7 +21,7 @@ is not always obvious because of the coherences between SSL, HTTP and Apache's 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. @@ -121,7 +121,7 @@ find in the README.GlobalID document in the mod_ssl distribution. 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 diff --git a/docs/manual/ssl/ssl_reference.html b/docs/manual/ssl/ssl_reference.html index f7ecb633ff..08e52ffb5c 100644 --- a/docs/manual/ssl/ssl_reference.html +++ b/docs/manual/ssl/ssl_reference.html @@ -600,7 +600,7 @@ in the global server context because the PRNG is a global facility. The following source variants are available:
    • builtin -

      This is the always available builtin seeding source. It's usage +

      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 @@ The following source variants are available: find under rndcontrol(8) on those platforms. Alternatively, when your system lacks such a random device, you can use tool like EGD - (Entropy Gathering Daemon) and run it's client program with the + (Entropy Gathering Daemon) and run its client program with the exec:/path/to/program/ variant (see below) or use egd:/path/to/egd-socket (see below).

      @@ -974,7 +974,7 @@ The available (case-insensitive) protocols are: 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.

    • All

      diff --git a/docs/manual/ssl/ssl_reference.wml b/docs/manual/ssl/ssl_reference.wml index db6ad65f53..1c49d178b9 100644 --- a/docs/manual/ssl/ssl_reference.wml +++ b/docs/manual/ssl/ssl_reference.wml @@ -259,7 +259,7 @@ The following source variants are available:

      • builtin -

        This is the always available builtin seeding source. It's usage +

        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 @@ The following source variants are available: find under rndcontrol(8) on those platforms. Alternatively, when your system lacks such a random device, you can use tool like EGD - (Entropy Gathering Daemon) and run it's client program with the + (Entropy Gathering Daemon) and run its client program with the exec:/path/to/program/ variant (see below) or use egd:/path/to/egd-socket (see below).

        @@ -513,7 +513,7 @@ The available (case-insensitive) protocols are: 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.

      • All

        -- 2.40.0