Repository navigation
Sandboxie Classic 5.73.4: causal telemetry for RunSandboxed request, child and reply? #5671
Unanswered
desarrolloinforhard
asked this question in
Q&A Feedback
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello maintainers,
Does unmodified Sandboxie Classic 5.73.4 provide supported telemetry that independently links a RunSandboxed request to the child created by SbieSvc and the reply sent to the original requester? We are evaluating an isolated test environment and need this evidence before proceeding with the target application. This is a capability/documentation question; we are not reporting a confirmed defect.
Our source review is pinned to the v1.18.4 / 5.73.4 release commit:
487d563.
This is a scoped source review, not a claim that the installed binaries have been proven equivalent to that source. Our earlier local inventory reported SbieSvc/SbieDll 5.73.4 and SbieDrv 5.73.2; please clarify whether that component combination affects the answer. We have not changed the installation for this inquiry.
Required evidence
For each invocation of MSGID_PROCESS_RUN_SANDBOXED, we need to correlate:
The source must be independent of assertions generated solely by the requester or test application. Containment checks (sandbox identity, SID and exact job membership) are additional checks, not a replacement for this causal chain. We are not assuming protection against a compromised Windows kernel or a malicious administrator.
What we reviewed
Questions
A. Does unmodified 5.73.4 expose a supported interface meeting these requirements: monitor records, an event provider, a diagnostic API, or another mechanism? If so, could you point us to the exact event schema/API and versioned implementation?
B. Which records tie the authenticated caller, request, child creation and reply dispatch together? What are the correlation identifier's uniqueness/lifetime rules, and what happens with concurrency, fragmentation and retries?
C. Where are those records generated, and how can the observer distinguish genuine broker/driver evidence from caller-generated diagnostic messages? How are process identity reuse and event loss handled?
D. What minimum access rights, settings, components, architecture constraints and restarts are required? Is the functionality available with Classic 5.73.4? We cannot currently expand privileges, inject into or attach a debugger to SbieSvc, replace service/driver binaries, or modify the service implementation. We are currently doing documentation-only research and will not enable any proposed tracing before a separate review. If the mechanism requires any of those actions, please state that explicitly; we are not requesting a workaround around access controls.
E. What happens if the consumer crashes or disconnects? Can collection be stopped without suspending or terminating SbieSvc, leaving pending debugger exceptions, or leaving tracing/session state enabled? What cleanup is required?
F. If 5.73.4 has no such interface, is one documented in a later release, or would this require a new telemetry feature? A confirmation that the current traces are diagnostic only and cannot prove this chain would also help us make an architecture decision.
A minimal documented example using synthetic requester/child processes, showing the complete event sequence and an incomplete/lost sequence, would be especially useful. We are not asking you to execute our application or access business data.
References
https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.18.4
https://sandboxie-plus.github.io/sandboxie-docs/Content/SandboxieTrace/
https://sandboxie-plus.github.io/sandboxie-docs/Content/LogMessageEvents/
https://github.com/sandboxie-plus/Sandboxie/blob/487d56309fafe90e2771d4c9004333fe01b77094/Sandboxie/core/dll/callsvc.c
https://github.com/sandboxie-plus/Sandboxie/blob/487d56309fafe90e2771d4c9004333fe01b77094/Sandboxie/core/dll/trace.c
https://github.com/sandboxie-plus/Sandboxie/blob/487d56309fafe90e2771d4c9004333fe01b77094/Sandboxie/core/svc/ProcessServer.cpp
Thank you for helping us distinguish supported observability from correlations that would remain inconclusive.
All reactions