From: Steve Sheppard <ssheps@gmail.com>
Date: Tue, 23 Nov 2010 17:11:48 +0000 (-0500)
Subject: add info on installing and configuring public key certificate systems;
X-Git-Tag: sprint4-merge-nov22~4203^2~282
X-Git-Url: https://old-git.evergreen-ils.org/?a=commitdiff_plain;h=9ec8a65e8c9478594ed4f06de4fbb34eeb56dc27;p=working%2FEvergreen.git

add info on installing and configuring public key certificate systems;
---

diff --git a/1.6/admin/serversideinstallation.xml b/1.6/admin/serversideinstallation.xml
index 7ea420ee05..20adc19fb8 100644
--- a/1.6/admin/serversideinstallation.xml
+++ b/1.6/admin/serversideinstallation.xml
@@ -672,7 +672,7 @@
 					<systemitem class="service">math</systemitem> service:</para>
 					<screen>
 						<userinput>/openils/bin/srfsh</userinput>
-						<computeroutput>srfsh# <userinput>request opensrf.math add 2 2</userinput></computeroutput> 
+						<computeroutput>srfsh# <userinput>request opensrf.math add 2 2</userinput></computeroutput>
 						<computeroutput>Received Data: 4</computeroutput>
 						<computeroutput>------------------------------------</computeroutput>
 						<computeroutput>Request Completed Successfully</computeroutput>
@@ -981,8 +981,8 @@
 					following commands:</para>
 					<screen>
 						<userinput>cd /openils/conf</userinput>
-						<userinput>cp opensrf.xml              opensrf.xml.BAK</userinput>
-						<userinput>cp opensrf_core.xml         opensrf_core.xml.BAK</userinput>
+						<userinput>cp opensrf.xml	      opensrf.xml.BAK</userinput>
+						<userinput>cp opensrf_core.xml	 opensrf_core.xml.BAK</userinput>
 						<userinput>cp opensrf.xml.example      opensrf.xml</userinput>
 						<userinput>cp opensrf_core.xml.example opensrf_core.xml</userinput>
 						<userinput>cp oils_web.xml.example     oils_web.xml</userinput>
@@ -1116,7 +1116,7 @@
 									user, perform the following commands:</para>
 									<screen>
 										<userinput>cd /home/opensrf/Evergreen-ILS-1.6.1.2</userinput>
-										<userinput>cp Open-ILS/examples/apache/eg.conf        /etc/apache2/sites-available/</userinput>
+										<userinput>cp Open-ILS/examples/apache/eg.conf	/etc/apache2/sites-available/</userinput>
 										<userinput>cp Open-ILS/examples/apache/eg_vhost.conf  /etc/apache2/</userinput>
 										<userinput>cp Open-ILS/examples/apache/startup.pl     /etc/apache2/</userinput>
 									</screen>
@@ -1234,8 +1234,7 @@
 											changes increase the number of Apache server
 											processes that are started to support additional
 											browser connections.</para>
-											<para>As the <systemitem
-											class="username">root</systemitem> user, edit the
+											<para>As the <systemitem class="username">root</systemitem> user, edit the
 											Apache configuration file
 											<filename>/etc/apache2/apache2.conf</filename>,
 											locate and modify the section related to
@@ -1243,10 +1242,10 @@
 											the load on your system:</para>
 											<programlisting language="xml"><![CDATA[
 <IfModule mpm_prefork_module>
-   StartServers           20
-   MinSpareServers         5
-   MaxSpareServers        15
-   MaxClients            150
+   StartServers	   20
+   MinSpareServers	 5
+   MaxSpareServers	15
+   MaxClients	    150
    MaxRequestsPerChild 10000
 </IfModule>
 ]]></programlisting>
@@ -1489,7 +1488,6 @@
 			expected.</para>
 			<simplesect xml:id="serversideinstallation-testing-connections">
 				<title>Testing Connections to Evergreen</title>
-
 				<para>Once you have installed and started Evergreen, test your connection to Evergreen. Start the
 				<command>srfsh</command> application and try logging onto the Evergreen server using the default
 				administrator username and password. Following is sample output generated by executing
@@ -1579,10 +1577,19 @@
 				<title>Configure a permanent SSL key</title>
 				<para>In a previous step (see <xref linkend="serversideinstallation-createcertificate"/>)
 				you used the command <command>openssl</command> to temporarily
-				create a new SSL key for the Apache server. This self-signed certificate was adequate
+				create a new SSL key for the Apache server. This self-signed security certificate was adequate
 				during testing and development, but will continue to generate warnings in the Staff Client 
 				and browser. For a public production server you should configure or purchase a signed SSL
 				certificate.</para>
+				<para>There are several open source software solutions that provide schemes to generate and
+				maintain public key security certificates for your library system. Some popular projects are
+				listed below; please review them for background information on why you need such a system and how
+				you can provide it:</para>
+				<itemizedlist>
+					<listitem><ulink url="http://www.openca.org/projects/openca/">http://www.openca.org/projects/openca/</ulink></listitem>
+					<listitem><ulink url="http://sourceforge.net/projects/ejbca/">http://sourceforge.net/projects/ejbca/</ulink></listitem>
+					<listitem><ulink url="http://pki.fedoraproject.org">http://pki.fedoraproject.org</ulink></listitem>
+				</itemizedlist>
 				<warning>
 					<para>
 						<emphasis>The temporary SSL key was only created to expedite