| Author |
Message |
| cj716 |
Posted: Thu Apr 19, 2012 8:56 pm Post subject: |
|
| Buckslayr wrote: |
| I understand how to add those to power apps. Please explain how to allow guarded apps access to sbie container. Thanks. |
Buckslayr, replied to your pm over at Wilders with details.
..... you can move the container to user space by opening Sandboxie Control, dropping down the Sandbox menu and selecting 'Set Sandbox Container' from the list and pick a location on another partition or in the User folder. Done. It will now work with AppGuard.
Or leave the Sandbox in the default location and open AppGuard GUI - go to Guarded Apps tab, press the Settings button, then add, navigate to C:\Sandbox and select. When added to the list click the 'deny access' next to it and a drop down will allow you to select read/write. Click Ok and OK and you're done. AppGuard will then allow apps to write to the container.
Let me know if you need anymore.
Cheers |
|
 |
| cj716 |
Posted: Thu Apr 19, 2012 8:52 pm Post subject: Re: Appguard |
|
| disallowed wrote: |
| Does not work (7x64) SBIE 3.68 |
Does for me. Are you also adding SBIE container to allowed folder for guarded apps? Can also move container to user space. |
|
 |
| Buckslayr |
Posted: Thu Apr 19, 2012 5:52 pm Post subject: |
|
| cj716 wrote: |
New release of AppGuard (3.3.4.0) with PowerApps that resolves SBIE compatibility issues on x64 now available http://www.blueridge.com/index.php/products/appguard/consumer
As well as adding sandboxiercpss.exe,sandboxiedcomlaunch.exe, sandboxiecrypto.exe to Power Apps remember you need to allow gaurded apps access to the SBIE container unless (like me) you have moved that from the default location to user space.
Cheets |
I understand how to add those to power apps. Please explain how to allow guarded apps access to sbie container. Thanks. |
|
 |
| disallowed |
Posted: Wed Apr 18, 2012 10:33 pm Post subject: Appguard |
|
| cj716 wrote: |
| tzuk wrote: |
| I updated the Known Conflicts page to list AppGuard, please let me know if you have any updates on this problem. |
Fixed in AppGuard 3.3.2 beta if sandboxiercpss.exe,sandboxiedcomlaunch.exe, sandboxiecrypto.exe added to new power apps tab in AppGuard . Will post when in full release version.
Cheers |
Does not work (7x64) SBIE 3.68 |
|
 |
| cj716 |
Posted: Wed Apr 18, 2012 12:42 pm Post subject: |
|
New release of AppGuard (3.3.4.0) with PowerApps that resolves SBIE compatibility issues on x64 now available http://www.blueridge.com/index.php/products/appguard/consumer
As well as adding sandboxiercpss.exe,sandboxiedcomlaunch.exe, sandboxiecrypto.exe to Power Apps remember you need to allow gaurded apps access to the SBIE container unless (like me) you have moved that from the default location to user space.
Cheets |
|
 |
| cj716 |
Posted: Thu Apr 05, 2012 10:31 pm Post subject: |
|
| tzuk wrote: |
| I updated the Known Conflicts page to list AppGuard, please let me know if you have any updates on this problem. |
Fixed in AppGuard 3.3.2 beta if sandboxiercpss.exe,sandboxiedcomlaunch.exe, sandboxiecrypto.exe added to new power apps tab in AppGuard . Will post when in full release version.
Cheers |
|
 |
| cj716 |
Posted: Wed Nov 09, 2011 9:11 pm Post subject: |
|
| tzuk wrote: |
| .... please let me know if you have any updates on this problem. |
From Blue Ridge Networks:
We do have the concept of Power Applications in our enterprise version of AppGuard. Power Apps are immune from AppGuard protection whether launched from a guarded application or directly. We'll consider exposing this feature in the future for the consumer version, but we are really trying to keep the consumer version as simple as possible.
Looks like it might be on Known Conflicts for a while.
Cheers |
|
 |
| Dave53 |
Posted: Wed Nov 02, 2011 2:38 pm Post subject: |
|
We'll keep you posted tzuk.  |
|
 |
| tzuk |
Posted: Tue Nov 01, 2011 11:25 pm Post subject: |
|
No problem guys. With so many complex interactions between programs on the PC, I look at every problem report as a potential to make Sandboxie a bit better.
I updated the Known Conflicts page to list AppGuard, please let me know if you have any updates on this problem. |
|
 |
| Dave53 |
Posted: Tue Nov 01, 2011 7:33 pm Post subject: |
|
Thanks for taking the time to look into this tzuk. If the problem has nothing to do with variables in 64-bit Win 7, I wonder if it may be caused by differences in the way AppGuard works in a 64-bit environment. Hopefully their developer will have time to review this.
Your support is stellar as always.
Dave |
|
 |
| cj716 |
Posted: Tue Nov 01, 2011 4:34 pm Post subject: |
|
| Brilliant. Thanks |
|
 |
| tzuk |
Posted: Tue Nov 01, 2011 1:49 pm Post subject: |
|
| This aspect of Sandboxie works the same on 32-bit and 64-bit, but what fails in SandboxieRpcSs is actually Windows code from the SXS.DLL that is being invoked. I can't tell you if SXS.DLL on 32-bit Windows behaves differently than its 64-bit counterpart, but I don't think so. In any case, and as far as I know, that code in SXS.DLL shouldn't be trying to communicate with other processes. |
|
 |
| cj716 |
Posted: Tue Nov 01, 2011 1:13 pm Post subject: |
|
As always thanks for the time you have spent on this issue which is in effect nothing to do with your product. Your commitment to making Sandboxie compatible with other, even relatively obscure, products is laudible.
I will contact BRN. Before doing so though, as this is only an issue on 64 bit machines, can you confirm if Sandboxie works differently in this regard on 32 bit systems. If not it is likely the way BRN have chosen to implement 64 bit protection rather than differences in your own product causing different reactions on different OS's.
Thanks |
|
 |
| tzuk |
Posted: Tue Nov 01, 2011 9:58 am Post subject: |
|
Not sure what else I can suggest. I explained the problem:
When SandboxieRpcSs.exe is started by a guarded process, it seems to inherit the guarded status, and this causes AppGuard to interfere with correct operation of the Sandboxie WINSXS mechanism.
I think you have to contact AppGuard and ask them for a "strong" exception, i.e. a list where you can say that even though SandboxieRpcSs.exe was started by a guarded process, it should not be considered a guarded proces itself. |
|
 |
| cj716 |
Posted: Mon Oct 31, 2011 7:55 pm Post subject: |
|
Thanks Tzuk, but I had SandboxieRpcSs.exe in the Memory Guard exceptions and changing privacy to 'no' made no difference. Throws a SBIE2399 DcomLaunch fails with error 1066 then freezes up for a while then throws SBIE2204 Cannot start sandboxed service RpcSs (-1), SBIE2204 Cannot start sandboxed service DcomLaunch (-1) and SBIE2204 Cannot start sandboxed service RpcSs (-1) over and over until you force termination.
I'll try forcing in the default box to make sure its not my customisations.
Cheers
Edit: Tzuk, your suggestion works when AppGuard is set to high which is the default. I use locked-down. This may mean I can't use both together, Interested in your thoughts? |
|
 |