From: markt Date: Fri, 4 Jul 2008 07:52:17 +0000 (+0000) Subject: Fix 45310, 45308 and a couple of additional typos. Also use OpenSSL consistently... X-Git-Url: https://git.internetallee.de/?a=commitdiff_plain;h=4edad6f643157c7dabea9068daf17759f545dac0;p=tomcat7.0 Fix 45310, 45308 and a couple of additional typos. Also use OpenSSL consistently and fix a very long line. git-svn-id: https://svn.apache.org/repos/asf/tomcat/trunk@673943 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/webapps/docs/ssl-howto.xml b/webapps/docs/ssl-howto.xml index 8cf3dee00..22ef9e72e 100644 --- a/webapps/docs/ssl-howto.xml +++ b/webapps/docs/ssl-howto.xml @@ -198,16 +198,18 @@ via (among other things) OpenSSL and Microsoft's Key-Manager.

Each entry in a keystore is identified by an alias string. Whilst many -keystore implementations treat alaises in a case insensitive manner, case +keystore implementations treat aliases in a case insensitive manner, case sensitive implementations are available. The PKCS11 specification, for example, requires that aliases are case sensitive. To avoid issues related -to the case sensitivity of aliaises, it is not recommended to use aliases that +to the case sensitivity of aliases, it is not recommended to use aliases that differ only in case.

To import an existing certificate into a JKS keystore, please read the documentation (in your JDK documentation package) about keytool. -Note that openssl often adds a readable comments before the key, keytooldoes not support that, so remove the openssl comments if they exist before importing the key using keytool. +Note that OpenSSL often adds a readable comments before the key, +keytooldoes not support that, so remove the OpenSSL comments if +they exist before importing the key using keytool.

To import an existing certificate signed by your own CA into a PKCS12 keystore using OpenSSL you would execute a command like: @@ -216,7 +218,7 @@ keystore using OpenSSL you would execute a command like: -caname root -chain For more advanced cases, consult the OpenSSL -documententation. +documentation.

To create a new keystore from scratch, containing a single self-signed Certificate, execute the following from a terminal command line:

@@ -280,7 +282,7 @@ which contains further references for this issue.

-

If you are using APR, you have the option of configuring an alternative engine to openSSL. +

If you are using APR, you have the option of configuring an alternative engine to OpenSSL. <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="someengine" SSLRandomSeed="somedevice" /> @@ -450,7 +452,7 @@ values, depending on how you configured your keystore earlier:

keystoreType Add this element if using a keystore type other than JKS. - For example the *.p12 files from openssl can be used using PKCS12. + For example the *.p12 files from OpenSSL can be used using PKCS12. sslProtocol