Hi Patrick. Could you explain this a little further? Actually creating a
keystore using keytool of course has nothing to do with Tomcat per se, so I
assume you mean that the keystore created might not work with Tomcat. Under
what conditions would a keystore generated by one JDK not work with another
JDK? In testing, I was able to generate a keystore on a Windoze box with JDK
1.3.1, copy it over to a Linux box running 1.3.0, and successfully start up
Tomcat and access a page over SSL. If you have a properly-formatted JKS store,
why would it matter which JDK produced it?
Quoting Patrick Luby <[EMAIL PROTECTED]>:
> Hello,
>
> I have attached 3 patches that patch the following 3 documentation
> files:
>
> Attachment CVS File to Patch
> ---------- -----------------
> server-noexamples.xml.config.patch
> jakarta-tomcat-4.0/catalina/src/conf/server-noexamples.xml.config
> server.xml.patch jakarta-tomcat-4.0/catalina/src/conf/server.xml
> jakarta-tomcat-4.0/catalina/src/conf
>
> ssl-howto.xml.patch jakarta-tomcat-4.0/webapps/tomcat-docs/ssl-howto.xml
>
> The only change to each of the following 3 files was to replace
> "keytool" with
> "%JAVA_HOME%\bin\keytool" and "$JAVA_HOME/bin/keytool" in the
> documentation.
> This change is necessary because the keytool in the same $JAVA_HOME as
> is used
> by Tomcat must be used. Otherwise, keytool may fail.
>
> Patrick
>
> _____________________________________________________________________
> Patrick Luby Email: [EMAIL PROTECTED]
> Software Engineering Manager Phone: 408-863-3284
> Sun Microsystems
> 901 San Antonio Road, UCUP01-103
> Palo Alto, CA 94303-4900
> _____________________________________________________________________
>
- Christopher
/**
* Pleurez, pleurez, mes yeux, et fondez vous en eau!
* La moitié de ma vie a mis l'autre au tombeau.
* ---Corneille
*/
