DefenseWall GesWall & Sandboxie

Browsing the threads DefenseWall GesWall & Sandboxie carry a lot of respect here. And often Defensewall AND Sandboxie are used or suggested as a team.

With regards to browsers, isn't DefenseWall enough? I don't see the point of both DW & SBiE? e.g. If I surf with Firefox, DefenseWall's got it covered right?

(Similar question applies to GesWall, but I have never actually used it.)

 

thay do the same kind of job, which is to protect Internet facing apps, in different manners.

i'd recommend using only one of them to avoid conflict.

 

Though GW had a minor update earlier this year it seems all but officially abandoned. However, DW and SB are very actively developed and supported. You don't really need to use both. Keep in mind that 64-bit support leaves you with SB as DW is only 32-bit (for now).

 

I have used both DefenseWall and Sandboxie for quite a while now and I have never experienced any conflict.

 

I'm really not familiar with either of these yet. Isn't SB different in that everything is free to open etc UNLESS ordered into the Sandbox whereas DW confines all as untrusted from the get-go? I am off the mark there?

 

Although not explictly mentioned in the title of this thread, AppGuard is a possible replacement for DefenseWall on 64-bit systems, and is also compatible with Sandboxie.

 

Appguard was too daunting for me. My first mission was to allow my sandboxied Browser net access. It stumped me. Ended up reaching for my trusty Revo & uninstalled it. Granted if I had more patience I would have finally figured it out, but really how do they expect to sell it to the average joe? Defensewall wins hands down for simplicity.

 

agree

 

There is another current thread about downloading & running SpyShelter keylogger test, DefenseWall passed but Sandboxie didn't do anything. So isn't that a plus to DW over SB or is their a way for SB to handle keyloggers?

 

If the keylogger was run in the sandbox it could potentially be blocked.

 

Maybe someone can tell me how. I failed.

 

Make the keylogger run in the sandbox but don't give it internet access.

He can still register yuor strokes but can't transfer them.

When sandbox is closed..........keylogger is gone.

 

Better yet only allow your browser, maybe adobe and anything else you need to run in your sandbox. Then only allow your browser internet access. Anything else that tries to run won't be able to.

 

As others do, I setup my various sandboxes to only allow the programs I want to run. If they don't need net access, then they don't get it. Default deny is powerful.

Occasionally you'll run across programs that just won't run if there are any start/run restrictions - so the next best thing is to deny net access to anything but the relevant programs.

The limitation of relying on 'internet access restrictions' is that keyloggers and trojans can inject themselves into the browser process in order to bypass firewalls. Without realising they are doing it, this means they could bypass Sandboxie's restrictions as well.

 

I think I completely forgot I was running AppGuard!

 

There are some here that would offer you any assistance necessary for you to run AG should you try to give it a try again. I recently added SB to my setup and once it is configured it is quite a powerful, yet quiet combo.

 

God willing I'll take you up on that offer in a week or two to bring me up to speed on AppGuard. I grabbed a paid version of Sandboxie today and I am pleased with it muchly. Especially as I found that my keylogger & trojan attacks tests beat me due to my config. error & not SandBoxie.

I like this SandBoxie.

And you say AppGuard is a good companion rater than an overlap?

I'll take that as endorsement that AppGuard is a politely quiet HiPS.