I figured out the problem.. when the purchasing folks signed away for
the cert, they did not select "Apache", but accepted the default. "Old
Server Cert", whatever the heck that is... I generated a new CSR, sent
that to verisign, selecting Apache as the cert type, got back the cert,
did the keytool magic, ,and Voila!
Thanks for all the troubleshooting assistance!!
Jeff
Jason Bainbridge wrote:
On 4/27/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Is a chain cert really *required*? I see for an older selfsigned
cert that a chain cert was not part of the keystore file.
Well for self signed no as it isn't part of a chain, the chain is
required for trusted certs to prove that it is trusted by an authority
that users trust ike Verisign as they have the ROOT verisign
ceritificate in their browser.
Regards,
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
