"Michael T. Babcock" wrote:
> I believe I once saw on the Equifax site that they use signing certificates signed
> by Thawte -- so its possible that their certificate is not in the browser but that
> the browser can verify the Equifax certificate against the Thawte cert, and then
> verify yours ag
Jason Keltz wrote:
> Can someone explain why the server has to pass along the certificates from
> the CAs though? I don't quite understand. I'm new to this all. Isn't it
> up to the server to send out just the certificate, and then up to the
> client to do the checks? I mean, isn't it counter
Jason Keltz wrote:
> Can someone explain why the server has to pass along the certificates from
> the CAs though? I don't quite understand. I'm new to this all. Isn't it
> up to the server to send out just the certificate, and then up to the
> client to do the checks?
On one side, it's becaus
Lutz -- you rock!! That fixed the problem!!
Can someone explain why the server has to pass along the certificates from
the CAs though? I don't quite understand. I'm new to this all. Isn't it
up to the server to send out just the certificate, and then up to the
client to do the checks? I mean
On Thu, Dec 07, 2000 at 09:17:11AM -0500, Jason Keltz wrote:
> Finally, if I try to connect to the IMAP SSL server with Netscape
> Communicator v4.75 and v6 -- the *SAME* Netscape Communicator that talks
> to our SSL enabled web server without complaining suddenly says that it
> does not does not
Hi..
My department has purchased two certificates from Equifax Secure --
one for our SSL-enabled web server (www.cs.yorku.ca), and the other for
our SSL-enabled IMAP mail server (mail.cs.yorku.ca).
For the web server, we are using Apache 1.3.14 + SSL 1.42.
For IMAP, we are using University of Wa
