AppGuard 3.x 32/64 Bit

Hi Barb,

Congratulations on the new release; I've just updated and it's running great here. As Peter2150 said, an excellent product keeps getting better with every new release. If I were allowed only one real-time security application on my system and were forced to choose, it would have to be AppGuard.

BTW, congratulations also on the new website - it looks really cool.

Regards
pegr

 

I would also like to add my congratulations for a great job on the new release!

Dave

 

Congrats on this new release.Kind regards

 

Oh Yes indeed.

 

Agree, Yes Indeed

 

just updated running very smooth,thanks appguard

 

Yes, well done all at BRN.

The Power Apps in particular will increase the useability and compatibility of the product significantly but the other changes are equally as welcomed. Nice to see a company that reacts to user requirements and feedback.

Light, fast and rock-solid security. Keep up the good work!

 

Congratulations on the new release - a terrific product continues to get better!

 

nice program and it doesnt slow down nothing at all in any systems 32 or 64

 

Will adding sandboxie to powerapps solve any conflicts or is there still more needing to be done?

 

I just added SandboxieRpcSs, SandboxieDcomlaunch and SandboxieCrypto.dll to PowerApps which were added to Memory Guard Exception List in AppGuard 3.2. I run AppGuard in Locked Down mode and added the sandboxie container file to user space. If you don't guard applications that run sandboxed you won't experience any issues I guess.

EDIT: just tested some applications. It seems powerapps really does a good job. I can run sandboxed applications guarded without any issues so far. So I assume everything got easier to configure with powerapps. Thats even stronger protection guarding an application that runs sandboxed. I'm amazed. Thanks to BlueRigdeNetworks

 

I'm not sure now Sandboxed apps will also be guarded. The reason I'm unsure is the new version of power apps runs child process of the power app unguarded as well. So as SBIE forced apps invoke SandboxieRpcSs which is a power app could this mean the forced app if it is a child of SandboxieRpcSs is also a power app - so unguarded. Depends on the order things happen? Anyone confirm?

Thanks

Edit:clarity

 

Arkanex,
Do you have any issues with AppGuard and Rollback Rx. Thinking about installing AppGuard into an RbRx snapshot but was unsure about what I need to do, if anything about MBRGuard functionn of AppGuard. Thanks for SBIe input as well.

Gary

 

Rollback RX modifies the MBR on install so AppGuard would prevent it if it was already installed. As you've got Rollback installed first you should be OK. Nothing particular needed.

Cheers

 

Thanks Chris,
Someone mentioned somewhere that if you ever uninstall Rollback Rx you might have to disable MBRGuard in AppGuard first so uninstall process will be complete. But, thanks for your input because that is my concern now.

Gary

 

No problem huntyc, I actually tried this combo last week on Win7 x 64 (was thinking about the RX BDJ deal) and just reverted to a pre-AppGuard snapshot and deleted the AppGuard snapshot and all gone. Difficult if you're looking at AppGuard long term I admit and pre install snapshots get old I suppose.

Cheers

 

Since I don't know how Sandboxie works, I'm not sure if having child processes becoming power applications is going to result in "Sandboxed" apps not being guarded. To check it out, from a Sandboxed Guarded application, try saving to a protected resource and see if AppGuard blocks. A protected resource would be c:\windows, or C:\ folders. UAC may get in the way (or actually overrule AppGuard's block) so you may want to set up a protected folder in your user profile directory for this experiment). Make sense? If not, email me at AppGuard@BlueRidgeNetworks.com.

Let us know. Maybe we will need to make power app inheritance optional or roll back that change.

 

Makes perfect sense Barb, thanks. Tried that by adding a direct access file path in SBIE to a folder protected by AppGuard. The download was blocked so Apps are guarded when sandboxed. Excellent.

A word of caution for those using both though that the sandbox container either needs to be in user space or guarded apps allowed read/write to it. So real system files blocked by AppGuard like C:\Windows becomes C:\Sandbox\...\C\Windows when sandboxed so might not be subject to AppGuard restriction (they would of course be blocked if recovered to the real system). Dropping rights in SBIE prevents access to these files anyway or on Vista and 7 at least elevation would be required. I'll try to test later but anyone know already?

Cheers

 

I'm very new to Sandboxie and not quite following above posts. Is it a good combo with Appguard? If so, is it simple enough to add sandboxie folder to power apps?

 

buckslayr, yes they are a great combo and simple to set-up. Adding the SBIE apps SandboxieRpcSs, SandboxieDcomlaunch and SandboxieCrypto to Power Apps and either moving the sandbox container (default C:\Sandbox) to user space or allowing guarded apps to read/write to the sandbox at its default location and you're good to go.

My points above are only so I understand how the apps fit together. I really want to know whether AppGuard recognises its protected/gaurded files/folders if they are recreated inside the sandbox container thereby changing their location.

I don't believe it will impact protection either way as if something tried to write out of the sandbox to the real system AppGuard would block it anyway and SBIE will protect whats inside the Sandbox. I'm just interested in the mechanics thats all.

Cheers

 

Thanks Chris!

 

Thanks for the feedback!

 

Ok set file D:\Test as denied folder in AppGuard. Tried to save Word doc to it with Word guarded but un-sandboxed. Access Denied
Sandboxed/guarded Word with direct access path to D:\Test in SBIE. Access Denied
Sandboxed/ guarded Word with quick recovery to D:\Test in SBIE. Access Denied
Sandboxed/guarded Word with NO direct access or quick recovery to D:\Test in SBIE. File written to R:\Sandbox\User\Word\Drive\D\Test.

So it looks like as suspected AppGuard blocks the changes in the real system but does not recognise sandboxed versions of gaurded/restricted folders not recovered to the real system. Of course having the Sandboxie container in user space prevents unsolicited execution anyway so not really an issue but maybe worth noting for those like me who are interested in such esoterica.

Cheers

 

I *think* I understand.