Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

FireFox 3.0.7 - SSL problem


  • Please log in to reply
1 reply to this topic

#1 hellknight

hellknight

  • Members
  • 120 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Netherlands
  • Local time:01:01 AM

Posted 12 March 2009 - 12:01 PM

Since a few days, I find myself unable to acces a lot of SSL protected sites (https://) - for example, Paypal.
Firefox gives me the following error:
www.paypal.com uses an invalid security certificate.

The certificate is not trusted because the issuer certificate is unknown.

(Error code: sec_error_unknown_issuer)

When this kind of error occured in the past, I was able to add an exception, but that option isn't there.
I've tried to find what setting in FF causes this, but have been unable to. Doing a google search gives me lots of results, but no solutions.
IE7 opens the same sites without problems.

BC AdBot (Login to Remove)

 


#2 hellknight

hellknight
  • Topic Starter

  • Members
  • 120 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:The Netherlands
  • Local time:01:01 AM

Posted 18 March 2009 - 01:14 PM

A short update - should others face this problem one day, they might find this topic, and find at least some help thus.
With the aid of the Mozilla chat support, I changed the value of "browser.xul.error_pages.enabled" to "enabled", thus enabeling me to add an exception for sites, and view the certificates of sites that were blocked.
Thus, I noticed that the issuer of the certificate was listed as ESET, instead of, for example, verisign, etc - it appears that the newest version of ESET NOD32 (4.x) does something with the root certificates of sites you attempt to load, that Firefox does not like. The problems did start around the time I upgraded to the newest version of NOD32.
I was unable to find any option dealing with this in the settings of NOD32, so I've sent a support request to ESET.
Once that is anwered, I'll update this topic again




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users