Find out what browser types and versions you expect your users to use and go see what CA certs are preloaded into them. That's the list of CAs you should choose from. Getting a server cert from anyone else, or generating your own, will cause your user's browsers to popup the "invalid site" warning.
/s.
On Friday, March 14, 2003, at 12:04 PM, Michael Roberts wrote:
It's been a while since I bestirred myself to change anything in my SSL configuration (yes, I'm *still* running AOLserver 2.1 on one server...) but I've got reason to consider SSL on one of my newer servers and I don't want to pay Verisign more than I have to (and it's a different domain name). So what are the options in this brave new century for SSL certificates that won't make typical browsers choke?
Michael
I. To remove yourself from this list:
Send a message to "[EMAIL PROTECTED]" with the following text in the BODY of your message:
signoff aolserver
II. For a complete list of listserv options please visit:
http://listserv.aol.com/
III. For more AOLserver information please visit:
http://www.aolserver.com/
I. To remove yourself from this list:
Send a message to "[EMAIL PROTECTED]" with the following text in the BODY of your message:
signoff aolserver
II. For a complete list of listserv options please visit:
http://listserv.aol.com/
III. For more AOLserver information please visit:
http://www.aolserver.com/
