Sandboxie-Plus 1.0.17

No it means with an over-the-top install it will stay off, despite the intention for it is to be now on for all users.
To fix that I could have had changed the setting name, but I though its ok as is and people should enable it by hand, if they have an old install.

EDIT: the thing about this feature is that its quite usefull but the old sbie did not use it instead doing own per sys call filtering, with this object callback feature the filtering is more thorough, meaning if a relevant sys call is missed like the GetNextThread from the recent security fix, it will be inconsequential. Remember the workaround for that was to enable this filter.

 

It became a constant nag, so I uninstalled SB+ (keeping settings) and reinstalled as administrator, and so far the problem seems to have resoloved.

[EDIT] I spoke to soon! Now reverted to .15 and all seems ok again

 

Yea i think i know how it happened but I'm not sure why there should be no empty log lines, but somehow there sneaked one in, will be fixed in the next build.

 

firefox 98.0.2 running fine here, also v100-nightly. must be something special on your system or sb config.

 

btw i still consider this as a translation error. i have noticed it versions before and wrote about.

 

I have installed the classic KeePass + Sandboxie Classic 5.55.16 and everything is fine. Auto-Type in KeePass works fine.

 

Enabling the trace logging before starting sandboxed app causes sandman.exe to crash.

 

Confirmed on here, Sandman crashes when trace logging enabled--prior to launching Firefox.

Plus 1.0.16

Edit: here is snip of message. Is the dump needed also?

Spoiler

 

Sandboxie Classic v.5.55.16 64Bit - It works very well

 

I will add a checkbox soemware: "Allow sandboxed programs to read memory of unsandboxed once (not recommended)" or alike to add and remove this preset but i really ting this should not be on by default.
even if this now breaks some usecases, its simply ridiculously negligent to allow sandboxed programs to read the memory of unsandboxed once, like a exploiter chrome reading all the memory of your keepass.
I'm really puzzled why the original sbie devs allowed for that.

 

With current Chrome_v.100.0.4896.60 (Official Build) (64-bit) and new Sbie-Plus_v.1.0.16 I get numerous pop-up-error-notifications soon after start - although the browser itself seems to work fine in spite of those.

Latest Opera on the other hand does not show these messages and so far seems to run without issues.

 

oh yes googles software spy trying to spy on your software and sandboxie preventing that good error messages

 

given that I expect there may be more of them but that despite fo them most things shoudl work fine...
should I set in in the UI such that this messages wil only be logged to the log but never cause a pop up?

 

I mean the right fix would be to set googles software spy to not be allowed to start in the box, or enable the BlockTelemetry template it blocks such tools

 

Nice. Any remedy to make those (benevolent) error-messages go away then? I can't dismiss them that quickly and in such great number?

 

you can use the option to hide them forever dosn't that work?

 

Perhaps as a checkbox-option in the Chrome-template to be ON by default?

 

What exactly do you mean by that? I've clicked on "Dismiss" in the pop-up window for about a dozen+ times - but that window is still full of them. So I assumed the "Dismiss"-button would only kill them temporarily.

 

Update: Neither the "Hide all such messages"-button in the pop-up-window NOR enabling the "telemetry"-template did the trick. The pop-up-window is still flooded with error-messages on each Chrome-launch.

 

Next update: Perhaps I haven't been patient enough. After having clicked that "Hide all such messages"-button for a dozen or so times it now seems those error-messages may have gone for good. Looks now as if those may have been different specific errors which had to be dismissed individually - although appearing under the same general error-number.

Interesting observation: Now the Chrome-tray-icon will display an overlaid green progress-bar "scanning" for 4 times over the icon shortly after each launch of Chrome. But so far it seems the browser works normally after that and the pop-up-errors have stopped, too, after dismissing them all.

 

New build, it hides all process access messges thay are only shown in the UI log in the plus UI, the crash is fixed and the logging improved the errors now tell you what exact process was accessed

Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/1.0.17

Added

• added checkbox to easeli allow read access to memory of unsandboxed processes (old sbie behavioure, not recommended)

Changed

• improved OpenProcess/OpenThread logging

Fixed

• Fixed crash issue with the new monitor mode
• Fixed issue with resource access entry parsing

 

and here the old behavior can be enabled