That's a good works and we should in with my tomcat-ssl-howto.html :)

There is still things to be mentioned like :

- how to import OpenSSL, Thawte or Verisign WebServer certificates.
- in case of client authentification, how the stuff works.
 
  2 cases :

  You start you're own CA, using openca (www.openca.org) or part of 
  jonama works (www.multimania.com/jonama/). Then you generate both
  client certs and web-server certs with the newly created CA. Don't
  forget to import the CA cert ....

  You're using Thawte or Verisign or other major CA providers and
  in that case you should import the CA cert.

  That kind of question cover about 95% of the question on 
  tomcat-ssl-howto.html and I saw with your works a great occasion 
  to have a better documentation :)))) 

  What about merging ?

 

-
Henri Gomez                 ___[_]____
EMAIL : [EMAIL PROTECTED]        (. .)                     
PGP KEY : 697ECEDD    ...oOOo..(_)..oOOo...
PGP Fingerprint : 9DF8 1EA8 ED53 2F39 DC9B 904A 364F 80E6 



>-----Original Message-----
>From: Christopher Cain [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, August 16, 2001 8:12 PM
>To: Tomcat-Dev
>Subject: New SSL HOWTOs
>
>
>While creating the 3.3 version of my SSL HOWTO, I also polished off the
>wording here and there and added a TOC and section marks for easier
>navigation. Attached are both the 3.3 and 4.0 versions of the file.
>Consider this 4.0 version to supercede the one I sent last night (or
>early this morning, as it were :-)
>
>If someone could please let me know for sure that adding extension JARs
>to the "{JDK_HOME}/jre/lib/ext" directory under JDK 1.1.8 effectively
>makes them "installed extensions" (makes them available without
>necessarily being in the CLASSPATH) just like in >= JDK 1.2. Other than
>that, I'm pretty sure the TC 3.3 version of the doc is valid for JDK
>1.1.8 environments as well. If someone a little more familiar 
>with 1.1.8
>could maybe give it a quick once-over and see if anything jumps out,
>that would be great.
>
>- Christopher
>

Reply via email to