[deployment-guide/comm-rel-14: 639/677] Minor rephrasing.

Jaromir Hradilek jhradile at fedoraproject.org
Sun Nov 14 23:56:05 UTC 2010


commit 735f9b8afc94f87be8f34466fe3ee0537cab15fd
Author: Jaromir Hradilek <jhradile at redhat.com>
Date:   Tue Oct 26 12:30:01 2010 +0200

    Minor rephrasing.
    
    Thanks to Andrew Ross for pointing this out.

 en-US/The_Apache_HTTP_Server.xml |   12 ++++++------
 1 files changed, 6 insertions(+), 6 deletions(-)
---
diff --git a/en-US/The_Apache_HTTP_Server.xml b/en-US/The_Apache_HTTP_Server.xml
index 11fc3d9..dbc9ff7 100644
--- a/en-US/The_Apache_HTTP_Server.xml
+++ b/en-US/The_Apache_HTTP_Server.xml
@@ -3913,16 +3913,12 @@ SSLCertificateKeyFile /etc/pki/tls/private/<replaceable>hostname</replaceable>.k
       </para>
       <screen>~]# <command>yum install crypto-utils</command></screen>
       <para>
-        This package provides a set of tools to generate and manage SSL certificates and private keys, and includes <application>genkey</application>, the Red Hat Keypair Generation utility that will guide you through the key generation process. To run it, use the <command>genkey</command> command followed by the appropriate hostname (for example, <systemitem class="domainname">penguin.example.com</systemitem>):
-      </para>
-      <screen>~]# <command>genkey</command> <replaceable>hostname</replaceable></screen>
-      <para>
-        You should be presented with a screen as shown in <xref linkend="figure-apache-mod_ssl-genkey-01" />.
+        This package provides a set of tools to generate and manage SSL certificates and private keys, and includes <application>genkey</application>, the Red Hat Keypair Generation utility that will guide you through the key generation process.
       </para>
       <important>
         <title>Important: Replacing an Existing Certificate</title>
         <para>
-          If the server already has a valid certificate and you are replacing it with a new one, specify a different serial number, so that client browsers are notified of this change, update to this new certificate, and do not fail to access the page. To do so, use the following command instead:
+          If the server already has a valid certificate and you are replacing it with a new one, specify a different serial number. This ensures that client browsers are notified of this change, update to this new certificate as expected, and do not fail to access the page. To create a new certificate with a custom serial number, use the following command instead of <application>genkey</application>:
         </para>
         <screen>~]# <command>openssl req -x509 -new -set_serial <replaceable>number</replaceable> -key <replaceable>hostname</replaceable>.key -out <replaceable>hostname</replaceable>.crt</command></screen>
       </important>
@@ -3934,6 +3930,10 @@ SSLCertificateKeyFile /etc/pki/tls/private/<replaceable>hostname</replaceable>.k
         <screen>~]# <command>rm /etc/pki/tls/private/<replaceable>hostname</replaceable>.key</command></screen>
       </note>
       <para>
+        To run the utility, use the <command>genkey</command> command followed by the appropriate hostname (for example, <systemitem class="domainname">penguin.example.com</systemitem>):
+      </para>
+      <screen>~]# <command>genkey</command> <replaceable>hostname</replaceable></screen>
+      <para>
         To complete the key and certificate creation, take the following steps:
       </para>
       <procedure>


More information about the docs-commits mailing list