Sandboxie-Plus 1.15.10, 1.15.11

BindAdapterIP Accepts one IP per line,
and it is not supposed to work with more then one IP of any given type.

So normally you set up one ipv4 bind ip and one ipv6 bind ip and that's it,
you can set up different per process, but you can not set up two for the same process.
That would not work it would just pick the first and ignore the rest.
The internal API call https://learn.microsoft.com/en-us/windows/win32/api/winsock/nf-winsock-bind accepts only one IP and can not be called multiple times in a row.

The purpose of this feature is to restrict communication to a specified host adapter (be that physical or virtual, like VPN),
it does not restrict what remote IPs can be communicated with as long as they ate reachable from the network the socket was bound to.

 

That's exactly how I had it set up at first. It's just very odd that IDM doesn't work with BindAdapterIP. BindAdapterIP=10.2.0.2 works with Zen, but for whatever reason downloads are not forwarded to IDM with BindAdapterIP. But it works without it, and to my knowledge, IDM doesn't require any special connection settings.

 

@n8chavez Try this setting:

Binds all except IDMIntegrator64.exe.

Code:

BindAdapterIP=!IDMIntegrator64.exe,10.2.0.2

 

That doesn't work either, and I have no idea why! Downloads are not being handed over to IDM and are handled by Zen. Unsandoxed, or without ]BindAdapterIP, downloads are sent to IDM.

 

@n8chavez Does IDMIntegrator64.exe start running in the sandbox when BindAdapterIP is set?

 

Nope. But the interesting this is that IDMIntegrator64.exe is not listed in the task manager even if BindAdapterIP in not set, and yet IDM works just fine. IDMIntegrator64.exe is allowed to run and has internet access within Sandboxie.

 

Thank you David, this fixed both Firefox update issue and Edge not auto deleting.

 

Any ETA on 1.5.12?