I prepared the CAs using the "make certificate TYPE=custom" option. Both the server
and the CA files look fine to me and are in their proper pews.
There were warnings about security depth being 0, but that is to be expected during
the creation process.
In the mod_ssl documentation the instruction asks that I 'fire up' Communicator and
use the Perl script loadcacert.cgi in the pkg.contrib directory to load the CA into
the browser.
Then I have to 'walk through the dialog boxes'.
Well, this is all too simple for me to comprehend. I can execute the script file and
it assigns the x509 type, determines the length and prints out the certificate data,
but that doesn't get into Communicator, so nothing really happens. How do I tie the
script output into Communicator to trigger what should be happening?
Or is there a more straightforward way???
Thanks,
George Walsh,
Managing Director
Travel Seewise Pacific Corp
--
George Walsh,
Managing Director,
Travel Seewise Pacific Corp
Vancouver Canada
__________________________________________________________________
Your favorite stores, helpful shopping tools and great gift ideas. Experience the
convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/
Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
