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

Decrypt and Scan HTTPS

Can someone explain to me, when I enable Decrypt and Scan HTTPS on my default Lan to Internet rule, users are now prevented from viewing any website that is only HTTP? We can no longer visit our own company website.



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

    have you installed the certificates on each users PC and are you scanning http as well?

    Ian

  • I have not installed the certificates yet but did have Scan HTTP enabled as well and still do. With decrypt turned off we can go to any website.

  • From my testings, once the HTTPS scanning is enabled, all connections are forced into a (transparent) proxy mode. Maybe there is something in there causing the issue?

    I've been testing HTTPS scanning and don't have issues with plain HTTP sites, but I also don't have many rules in my unit at all. 

  • having the same issue.  we have deployed the certificate to all clients but https scanning causes the sites to throw up a warning regarding incorrect certificate.  and unlike some similar warnings, these tend not to allow the user to click past the warning which makes things much worse.  

     

    We haven't found a solution as of yet.

     

    and as is typical for Sophos support, I navigated through several emails and phone calls with no suggested fix, just the constant threats of closing the case if I don't respond immediately.  uhhhg

  • Do you have any example sites that I could help double-check? I know with the deploying the required certificate across the network, you have to be sure you're deploying the correct one.

    Is there any mileage in the approach to deploying the cert? Personally I've been using the Trusted Root Certificate within Local Computer which seems to cover all basis for different browsers (IE and Chrome)

  • For myself with Decrypt and Scan enabled, I could not go to any site that was 'http' so URL was any site it automatically changed the URL to 'https', which wasn't available. I have not set up the Certs yet to retest but I was under the gun just to get this firewall in place but even so that didn't make sense to me what so ever behaving like that. I used our company site as my test which is not setup as a secure HTTP site and it added 'https' to the URL rendering it not available.