0 Members and 1 Guest are viewing this topic.
@ Asyn >>> no need to wake the thread either
Quote from: bri on May 14, 2010, 02:11:25 PMyou must not know how to use it because your telling me it doesnt do something when it does?Yeah, definitely... see, you need to run the malware sandboxed first to get it sandboxed by SBIE. What you've described here is that you downloaded some malware in Chrome and opened it and did run it. And you go and complain that Chrome sandbox didn't protect you? Seriously, t3h sigh. Will SBIE protect you in this case? Well, obviously not unless you - either right-click it and select Run sandboxed - or run it from a forced folder.
you must not know how to use it because your telling me it doesnt do something when it does?
I recently discovered a very nasty bug in the module sandbox. When enabled virtualization in Google Chrome, it refuses to work Adobe Flash Player.
QuoteI recently discovered a very nasty bug in the module sandbox. When enabled virtualization in Google Chrome, it refuses to work Adobe Flash Player.Got it, there was a hidden bug in registry virtualization... Fixed, thanks for feedback.
so it should be okay with Firefox too now (ie in the next build?) and plugins not loading when only web browsers are allowed to connect (from the sandbox setting panel)...
This Flash problem affected only Chrome browser.Quoteso it should be okay with Firefox too now (ie in the next build?) and plugins not loading when only web browsers are allowed to connect (from the sandbox setting panel)...sure and I'm also gonna include new features in next build.