Hi, Here https://www.webrootanywhere.com/sah_Identity_Protection.asp?n=About_Identity_protection it says, 'When you use a search engine, the Identity Shield analyzes all the links on the search results page and then displays an image next to each link that signifies whether it's a trusted site (green checkmark) or a potential risk (red X).'......but I don't see anything like this when I google something in firefox.....but in IE it shows ...... also identity shield does not work in sandboxed browser with sandboxie..... I've sent tzuk an email asking for the inclusion of wsa in the list if Software Compatibility ......don't know if he's gonna consider it..... can the wsa team do something about it......maybe ..um..ask tzuk officially to list wsa.....so that wsa and sandboxie can live in harmony in my pc........ Best Regards, ams963
I think compatibility with Sandboxie might be complicated due to our self protection and the fact that we randomize all of our interprocess communication channels on each communication, which means they wouldn't be able to make a rule without reducing security. Could you let me know what version of Firefox you're using so that I can take a look? And could you see if you're using the HTTPS version of google.com in Firefox or the normal HTTP? I've seen that the HTTPS blocks modification in some cases. Thanks!
so if I use sandboxie I'll not get wsa protection ...... I'm using firefox 8.0 and yes I'm also using https google in firefox.....
You still receive the antimalware protection from WSA, but not the additional layer of Identity Shield protection. However, if you only do online banking/shopping outside of the sandbox, you'll still receive the protection of the Identity Shield (and those are probably very low risk for compromise. It should work properly if you log out of Google which will return you to HTTP searches. We're looking into adding support for HTTPS searches but there are a handful of complexities involved.
@PrevxHelp and @Triple Helix thx both of you.......really appreciate it..... wsa has safe start sandbox.....is it similar to sandboxie........
well... so far what I've understood is...... when you use https it causes your google searches to go through an https connection (secure) rather than an http connection... since the https connection is encrypted wsa team cannot parse the results because wsa team cannot decrypt them...... if you sign out of gmail account or use yahoo for example you will see the search annotations....
hey....one thing....if wsa search annotation does not appear for https searches....then how come wot and bitdefender trafficlight shows their annotations or site ratings..... and wsa shows annotation in http searches just fine along with wot and traffic...and it's wonderful to see three ratings protecting me from malicious sites..... also in google.....wsa does not show rating or annotation in specialized searches like video or image searches ....even in http searches
The WSA search results work at the protocol level, not at the browser level, which makes them analyze the data much lower down and allow it to filter out malicious content before the browser sees it. For the search result annotation specifically, we will have to work from within the browser instead (which is what other applications do) as we have to sit above the SSL layer. Google has just recently started adding HTTPS searches and very few users are actually performing them yet so this isn't a very high priority change. If you click on a malicious link within an HTTPS search, we will still block it as normal. Hope that helps!
SafeStart isn't exactly the same as Sandboxie as Sandboxie tries to make the programs think they aren't in a sandbox so that they work normally and can store data as usual. SafeStart blocks access to external functions to prevent them from being used by malware so that you can test if software is malicious or not (and we show you the events coming from the program in realtime).
but the Webroot Support and Help is saying the Web Threat Shield feature Analyze search engines and identify malicious websites before visitation conflicts with Sandboxie and that is why it does not function in my sandboxed browser.......let me remind you that this feature is not a part of the Identity Shield but the main Web shield of Webroot SecureAnywhere......
That component of the Web Threat Shield will be affected by Sandboxie's protection as well. It falls into the same category as it needs to communicate back and forth outside of the browser.
