

Long story short - I'm not an expert in this area but I'm guessing that Norton Community Watch is probably just compiling background data on how often certificate checks are run with OCSP, and Symantec might even be cross-referencing details about those OCSP submissions to improve their own web browser protection and detection of expired/stolen certificates and malicious websites.ģ2-bit Vista Home Premium SP2 * Firefox ESR v52.8.0 * NS v22.14.0.54 * Malwarebytes Premium v3.5.1 since OCSP is not encrypted it is possible for an interested to party to intercept the communication and so, build a list of websites that a client visits". Malwarebytes quickly resolved the issue and stopped blocking Firefox submissions to, but that in8sworld blog points out that " if a website's certificate is stolen it can be used to impersonate that website and a web browser would not be able to tell the difference between the real website and a fake one. The 2017 blog post Malwarebytes Flags Firefox as Malicious for Checking Certificates? includes a discussion about an incident in late 2016 where several Malwarebytes Premium users were reporting false positive detections by their Web Protection module for (see one FP submission ).

OCSP does not mandate encryption, so other parties may intercept this information. OCSP discloses to the responder that a particular network host used a particular certificate at a particular time.

