On 4/9/2010 8:58 PM, David E. Ross wrote:
On 4/9/10 10:38 AM, JD wrote:
Martin F. wrote:
JD schrieb:
A web page that I trust appears to have let it's security certificate
expire and now I can't sign on. There window that pops up says:
www.changed-webpage-name.com uses an invalid security certificate.
The certificate expired on 06 Apr 10 15:55.
Error code: sec_error_expired_certificate
I have contacted them but it said they can take up to two days to get
back to me so is there a way to over-ride this setting in SM?
If this screen occurs:
http://img2.imageshack.us/img2/4539/exception.png
Click that you know the risk and then click on the button to Add an
excption which allows you to confirm a security exception for invalid
certificates in the upcoming window.
regards
Martin
I don't get that screen. I did get a e-mail from customer support and
they say they're aware of the problem and are working on it so I guess
I'll just wait?
Because Mozilla developers want to over-protect users, your problem is
one that cannot be resolved within SeaMonkey's capabilities. This is
not a SeaMonkey problem but a Mozilla Core problem.
See my bug #548380 at
<https://bugzilla.mozilla.org/show_bug.cgi?id=548380>.
I confirm that I never had this problem with SM 1.xx and that import of
certificate works adequately. One more reason for me to wait until SM
2.xx matures, I cannot afford this kind of situation for my personal
finances.
--
John Doue
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
