Discussion in 'Prevx Releases' started by GrammatonCleric, Nov 8, 2011.
Since Trusteer report is not.
Rather the SafeOnline portion of WSA (the keylogger hide).
WSA as a whole is compatible with Sandboxie but the SafeOnline replacement portion of WSA isn't compatible
Nothing gets in or out of Sandboxie. So if you have security running outside it, and something else running inside it, they can't talk to each other. That's what a sandbox is.
Webroot has my money, and I've got their product. Beyond that though it's been a waste. I assume it's because I run Firefox under Sandboxie, but Firefox freezes, leaving me no alternative other than a forced power-off.
I've installed WSA Antivirus three times, and removed it three times. I give up. I can't find a combination of settings that work.
Having used Prevx, I trust WSA to work as well. I won't give up running my browser sandboxed though. So, WSA is out for me.
Most others are a waiste when you have sandboxie.
Could you write into our tech support inbox so that they can work further with you? There shouldn't be any incompatibilities like this and I'm not aware of any similar case.
If you have any problem getting a response or getting it resolved, PM me with your email address so that I can take a look.
Whether you need Sandboxie or not really comes down to personal choice and what you do online. I actually started using Sandboxie to sandbox the browser following all the recommendations on here, but I find I use it less and less these days. The only time I use it is when I'm testing rogue-like applications and the like. My day-to-day browsing doesn't warrant the use of sandboxing techniques IMO. For example, I'm on Wilders now and only Wilders; should that session be sandboxed? I don't think it needs to be.
Even good websites can be hacked. A while back I was searching for some medical information and visited a normally good website that had been hacked, which tried to download a trojan. I had the WSA beta installed at the time and not a peep out of it. This is not a criticism of WSA as it is unrealistic to expect that a blacklisting product will stop everything. I had the browser sandboxed at the time though and Sandboxie contained the trojan.
Personally, I would always rely on a combination of virtualization and policy restriction for my primary defence. For me, blacklisting products are a second line of defence only.
I'm aware legitimate websites can and do sometimes become compromised. That's one of the downsides of the 'net, and it's no longer the thing to say bad stuff only happens when you trawl the darker corners of the web.
I'm curious though; did that trojan download via a script on that site? Some malware gets downloaded when a script is run, but if scripts are disabled, like with the use of NoScript on Firefox, there's less chance for those kind of things to happen. Of course, if domains are whitelisted in NoScript and one of them gets compromised, then NS isn't going to protect you in that instance either.
As we've heard many times on Wilders, a layered approach to security is considered to be a good way to protect oneself. The problem is outside of here, and other security fora, other computer users generally have no idea about these things.
I've no idea as I simply right-clicked on the Sandboxie tray icon and selected "Terminate All Programs" which did the trick in an instant. That's the beauty of Sandboxie: You can use the web normally without worrying. I did try NoScript once but I found it too much of a hassle. Sandboxie is much easier to manage.
My browser is always in sandboxie and its not just about virtulization for me, its a Antiexcutable,Internet access restrctions and access files protection and safe admin, it does what no others have for me.Nothing against WSA its a good security app, but it just cant do what sandboxie can do or is it ment to.To each there own I say and whatever works for you.We all like different things and have different opinions.
Lets keep to the topic please: Is WSA compatible with Sandboxie?
I didn't really have any desire to act as a beta tester. I bought the "finished" product with the expectation that it was as compatible as Prevx. Prevx permitted me to exempt the Sandboxie folder; so there was no problem with running my browser sandboxed.
I got a 3 user WSA, so I may be able to try it on my laptop. I reinstalled Prevx on this machine, and if WSA isn't compatible by the time Prevx support is gone, then I'll just look for other ways to secure my machine.
Had they provided a means to exempt my Sandboxie folder from WSA's intrusion, there would have been no problem.
I hate to say it, but welcome to the world of computers. By your stated logic, you're beta testing Windows. I know of no software that is 100% compatible with 100% of everything in every way possible.
Have you written to support?
The reason I ask is the fact that Sandboxie will always prevent SOL/Identity Shield operations from outside itself to affect things inside it. That means that the Identity shield in WSA is "Not compatible" with Sandboxie in the sense that Sandboxie makes it 100% impossible for such a system to operate. That being said, however, many users use Sandboxie "instead" of the Identity shield (Since it can't work) and have absolutely no problems with the browser such as you have had. So in the sense of being able to co-exist, they are fully compatible.
The only reason that any problems should be able to occur is if Sandboxie is allowing the browser to leak out of the sandbox enough to be detected by the ID Shield and then allows the ID Shield's attempt to connect to the browser to leak back in enough to cause problems for the browser. This implies that Sandboxie may not be configured sufficiently to properly sandbox the browser. If all else fails, check the Protected Applications list. If Firefox is listed as Protected, it's not fully sandboxed, and should be changed to "Allow" instead.
I guess this also applies to other sandboxing applications, such as Bufferzone. The answer is to disable SOL/Identity Shield when using any of these programs.
You shouldn't need to. WSA Identity Shield will automatically be disabled when using Sandboxie, but it shouldn't cause any conflicts and the browser should continue to operate normally.
One approach is to do all banking and shopping on trusted websites, where there is a risk of identity theft, outside of Sandboxie. For normal web surfing, where no personal information is entered, use Sandboxie.
One thing I'm not sure about is whether or not WSA Identity Shield attempts to verify the authenticity of the website in the way that Prevx SafeOnline and Trusteer Rapport try to do. Perhaps PrevxHelp or Triple Helix could clarify this.
WSA Identity Shield is the same as Prevx with SafeOnline but made stronger and compatible with newer Browsers! Here some info on WSA Identity Shield: http://www.webrootanywhere.com/sah_Identity_Protection.asp?n=About_Identity_protection
And I agree with pegr's advice!
Separate names with a comma.