We did solve the problem, and are fully on SSL3.0 now.  What the problem
was eludes me at the moment (asked a couple Ops guys offlist too) since
it's been a few months, but I'll try to dig this up for you tomorrow.

BTW - the problems stated below were causing a different type of
error; basically the page would not load if the browser did not support
SSL3 at all, without an error.

Charles Daminato
TUCOWS Product Manager
[EMAIL PROTECTED]

On Mon, 17 Dec 2001, Thomas Mon wrote:

> I found this in the archives.... from June 2001 --- Did you find out what
> this was?  We are considering trashing our Entrust certificate and just
> getting a Verisign one because of this issue.
> 
> ----- QUOTED FROM ARCHIVES 06/2001-----
> We're reverting back to SSL2.0 until we can figure out why (beyond all
> reason) this is causing issues.
> 
> Charles Daminato
> OpenSRS Product Manager
> Tucows Inc. - [EMAIL PROTECTED]
> ----- QUOTED FROM ARCHIVES 06/2001-----
> 
> Thanks!
> Tom.
> 
> 



Reply via email to