Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 3 subscribers
  • Views 11973 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

HTTPS Scanning in Web Appliance and its affect on Firefox

DC_IT_Manager

I recently turned on HTTPS Scanning on our Virtual Web Appliance.  I had to turn it off after about 15 minutes.  I was well aware that I would need to distribute the Sophos Web Appliance generated certificate before hand.  I did that successfully via GPO.  

When I turned it on, Google Chrome worked fine on HTTPS sites (with a few exceptions).  However, Firefox completely stopped working correctly - and you couldn't even click through to get to the HTTPS site - unless you added the site to the exception list - and that's impossible.

So why does the Sophos Certificate work for Chrome and not for Firefox?



This thread was automatically locked due to age.
Parents
  • 0
    Hi Adam,

    Mozilla designed Firefox to use it's own certificate store instead of using the Windows system certificate store, which is where your GPO pushed certificate is stored. In order to use HTTPS Scanning in Firefox, you would need to import the Sophos Root CA into Firefox.

    Fortunately Google designed Chrome to use the OS certificate store.

    Petr.
Reply
  • 0
    Hi Adam,

    Mozilla designed Firefox to use it's own certificate store instead of using the Windows system certificate store, which is where your GPO pushed certificate is stored. In order to use HTTPS Scanning in Firefox, you would need to import the Sophos Root CA into Firefox.

    Fortunately Google designed Chrome to use the OS certificate store.

    Petr.
Children
No Data
Unfiltered HTML