From: markt
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.
keystoreTypeJKS.
- For example the *.p12 files from openssl can be used using PKCS12.PKCS12.
sslProtocol