Enabling Webroot Filtering Extension causes safe "green padlock" sites to report a message that states "this page includes other resources that are not secure". This image should explain everything.
Already have an account? Login
Login to the community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
I am guessing though that it is the same one that I see... not the green padlock but the gray one with a yellow triangle.
Personally, I like it as I can easily tell the difference between a page in which ALL content is delivered from a secure server and which content, while OK, is not derived from the same source.
The gray-padlock-with-yellow-triangle is a native part of Chrome. You can see that icon when you go to a website that is SSL secure, but, say, embeds an image or banner or something from another server that isn't SSL secure.
The issue is that I never see any green padlocks when Webroot Filtering Extension is enabled. The extension acts as "something on the page that's embedded from another server". Thus, I can never tell the difference between a 100% secured website and once that's only partially secure.
Since I own and run an insurance website, I would very much like users to see the green padlock on my site. But if they have Webroot Filtering enabled, they'll only see the partially-secure icon... and it looks like it's my company's fault we're not 100% secure.
I have had a remote session with
So, hopefully we will get back the green padlocks even if the extension is enabled.
I appeal on Webroot to resolve this issue as soonest, for their own good!
Any progress in fixing this bug? ETA?
If you are in fact on .24 and Chrome is listed as Protected - Please submit this to the Support System so that we can begin to collect more info.
The ball is on your side.
Let me know if you have any questions!
So this is a Chrome issue and are Firefox & IE affected by this as I don't use Chrome?
Correct, this is only going to happen on Chrome (partly due to their sandboxing).
At the moment, Chrome does not have any workaround available for it. I'm checking if we could limit it to only search result pages (from the posts it sounds like it's happening on other pages as well - can someone confirm?)
The only solution I have found is to disable the Webroot extension, making my machine's SecureAnywhere solution less complete. But doing so doesn't solve the problem of any other Webroot users accessing my website arriving at the false impression that my site has a security issue. 😞 I do wish there were some sort of workaround.