Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding a troubleshooting wizard in Sandboxie #1875

Closed
isaak654 opened this issue May 20, 2022 · 6 comments
Closed

Adding a troubleshooting wizard in Sandboxie #1875

isaak654 opened this issue May 20, 2022 · 6 comments
Labels
added in next build Added in the next Sandboxie version Feature request New feature or idea

Comments

@isaak654
Copy link
Collaborator

isaak654 commented May 20, 2022

I would suggest adding a troubleshooting wizard in Sandboxie, which would be triggered automatically when an error is found, so that a detailed report can be saved and ready to be sent after user consent.

The report in question should match the same fields of the problem report template, or even more if needed.

In my opinion, it could be optionally extended to the Classic UI in order to cover the entire user base.

@isaak654 isaak654 added the Feature request New feature or idea label May 20, 2022
@isaak654 isaak654 changed the title Adding a troubleshooting wizard for the Plus UI Adding a troubleshooting wizard in Sandboxie May 20, 2022
@DavidXanatos
Copy link
Member

How to detect a failure? Many failure modes do not end with a crash. Often its the mouse not moving in some game, some window stay empty, or a custom message box with an error message.
Also by default trace log is off hence can't be provided for an unexpected failure.

I was thinking about some sort of troubleshooting wizard on and off for quite some time and I think it would need to be a user interactive wizard, not like Windows's typical wizards that work like: click next, I'll do something or not don't tell you what, and afterwards it may work, or not.

I think it would work something like this:
First the user has to select what sort of program he is trying to get working, that is, if the program as such is trustworthy or suspected to be malicious.
If its trustworthy we can proceed with the full process.

Full Process:
will try various insecure strategies including disabling token isolation, desktop isolation
followed by disabling system hooks, and security filtering
then disabling various DLL hooks
After each step querying the user once the process terminated if worked or failed,
On failure it would move to the next pass disabling more security/isolation
On success it would refine the last disabled measures to find the culprit

Limited Process:
will not disable security measures only try to skip some optional DLL hooks
and make a trace log

@bastik-1001
Copy link
Contributor

Whenever or not the wizard would be localized, it should be made clear that only reports in English can be processed properly.

Some programs send crash reports and if Sandboxie does the same I guess that it can be quite helpful to analyze crashes that are more widespread.

It should be stated where those reports are sent to and who has access to them, as they may contain private information.

The idea of a wizard that helps with configuring a certain sandbox in a way to run some software that otherwise fails to run, is interesting as well and it can potentially reduce the number of support requests. It should be made clear that there can be drawbacks to how Sandboxie can isolate/restrict programs, when features need to be disabled for them to run.

@isaak654
Copy link
Collaborator Author

isaak654 commented May 31, 2022

  • In case someone forgets the Sandboxie version that was previously working for a program, I think some kind of feature is needed to generate a history of all upgraded Sandboxie builds and obviously sorted by installation date.

  • The troubleshooting wizard should also be able to produce a list of all applied templates / browser extensions running in the faulty sandbox / installed apps

  • The reports should include information per sandbox and also at [GlobalSettings] level.

  • There should be a new SBIE message encouraging users to be informed about browsers regressions interactively, for example when vivaldi.exe is detected in the system:

@DavidXanatos reply:
mmhh... well yea you are right, but to do that nicely will need some changes, i think we need a compatibility wizard like the global one but on a per box level, that is whenever a new program.exe is started in a box, the UI component will check for available compatibility templates, and offer to activate them including a possible message about incompatibilities

@isaak654 isaak654 changed the title Adding a troubleshooting wizard in Sandboxie Adding a troubleshooting / compatibility wizard in Sandboxie Sep 18, 2022
@isaak654 isaak654 changed the title Adding a troubleshooting / compatibility wizard in Sandboxie Adding a troubleshooting wizard in Sandboxie Plus Apr 7, 2023
@isaak654 isaak654 changed the title Adding a troubleshooting wizard in Sandboxie Plus Adding a troubleshooting wizard in Sandboxie Apr 7, 2023
@DavidXanatos
Copy link
Member

I think this feature will be on the soon to be added agenda

@DavidXanatos DavidXanatos added the High priority To be done as soon as possible label May 25, 2023
@isaak654 isaak654 added added in next build Added in the next Sandboxie version and removed High priority To be done as soon as possible labels Jul 2, 2023
@bastik-1001
Copy link
Contributor

It's unclear to who has access to the reports (and the data) the user send in via this function. It's still new, so things might be subject to change, but it still could be clarified.

At least, the email address (if provided) can be considered confidential and users might wonder if those are transmitted and stored securely.

@DavidXanatos
Copy link
Member

The data are transferred via a TLS encrypted connection ans stored on the sandboxie-plus.com server, currently only I and a Friend who administrates the server have access.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
added in next build Added in the next Sandboxie version Feature request New feature or idea
Projects
None yet
Development

No branches or pull requests

3 participants