- Jun 2, 2018
- 96
Who cares of other forums. We are here. if this is rude for you, wait my answers the day you wrote nonsense stuff.It is considered rude in many fora. I am still new here.
Browser sandboxes and sandbox apps aren't the same; browser sandboxes are limited to web pages. Sandbox apps does more in term of overall security.Anyway. I am currently not using Sandboxie to sandbox my chrome. I think there are unanswered security questions. (global)
me, i will isolate your keyboard LOLUmbra- with SBIE, what would protect me when I'm on the Phone?
If you are skilled with sandboxie, you dont need an AV. AVs are obsolete in term of security, if they didn't have their HIPS or BB they would be useless.I am not sure that I can trust a program that hinders AV solutions to see malware running inside it. (See OP)
With sandboxie, you can block processes/programs to run in the sandbox in the first place; when my Chrome is sandboxed, it is the only program authorized to run in its sandbox; all other processes are blocked.Then consider this: Malware on a page interchanges google-update.exe (Which I would have to add to executable programs list in order to use Chrome inside Sandboxie) with it self. Now it can run inside the Sandbox. Also no antivirus detects it because Sandbox.
Or what about Malware-pages running a false chrome.exe? It could run no problem, (Since no hashing of allowed processes or anything similar) yet no anti-virus solution is able to see it. Then it simply writes code to RAM and executes it to escape the sandbox.
I can't take you as a serious tester when you don't know how the software works. And seriously? test-files...?I proved it's possible. With something as dumb as a TEST-FILE. I would consider this an EXTREME security flaw.
Please read again what I wrote: Any program with the name "chrome.exe" can run perfectly fine in a sandbox configured to only allow "chrome.exe". And it is irrelevant if it is a test-file or not. It could run perfectly fine inside it, but would get blocked if run outside.If you are skilled with sandboxie, you dont need an AV. AVs are obsolete in term of security, if they didn't have their HIPS or BB they would be useless.
With sandboxie, you can block processes/programs to run in the sandbox in the first place; when my Chrome is sandboxed, it is the only program authorized to run in its sandbox; all other processes are blocked.
Please learn the software before bashing it.
I can't take you as a serious tester when you don't know how the software works. And seriously? test-files...?
In paid version, you can force apps and folders to be automatically isolated in separate sandboxes, then you apply the desired policies to those. It is a huge difference.Yes I use free edition. So I can only create one Sandbox. And that means the downloaded chrome.exe will run in the same sandbox.
I forgot to mention that. But I didn't knew it's behavior would be so different.
And how does that work with Chrome? Chrome usually starts about 10 instances of chrome.exe. Does it mean you'll have this many sandboxes running? How is yet a another chrome.exe started by chrome a different case to all the other non-malicious chrome.exes?In paid version, you can force apps and folders to be automatically isolated in separate sandboxes, then you apply the desired policies to those. It is a huge difference.