Add SandboxieLogon selection to new box wizard

[bastik-1001]

Is your feature request related to a problem or use case?

SandboxieLogon can't be enabled by default, or isn't, since third-party security software does not like it, when this option is used with browsers running in them, when they inspect the TLS certificate or the encrypted traffic.

Since this can be helpful in isolating sandboxes from each other, users should be exposed to this setting, when they create new boxes and opt-in to configure advanced options. Right now, the exposure to this feature does not seem to be high.

Describe the solution you'd like

Add a checkbox, probably not checked, to enable SandboxieLogon to the box wizard.

Maybe, with a note (or tooltip) where users will be informed about potential issues with browsers in combination with some third-party tools, allowing them to decide if they can enable it, since they might use it for other purposes or do not run affected third-party tools. The sandbox options already have a description and the note, so it can be taken from there.

Describe alternatives you've considered

No response

[DavidXanatos]

this is a good idea, an other thought... when sandman starts and don't find a sandbox, should we show the box creation wizard for the default sandbox, instead of just creating silently one with default presets?

[bastik-1001]

when sandman starts and don't find a sandbox, should we show the box creation wizard for the default sandbox, instead of just creating silently one with default presets?

I don't know what the best approach is. If the first one is created silently, it can be used right away and the user does not need to do anything. This seems to be ideal for users that just start to use Sandboxie. On the other hand, it gives them control over what the box is being set to be used for. It might depend on the type of user. Maybe you can have some sort of survey to see that works best for most people.

[DavidXanatos]

hmm... you know what, the thin with new users is a good point, also this behaviorue would mean that after the 1st start wizard we would pop up the next one for the default Box, that is nto good UX, what we could do though would be to add a check box on the final page offering to open the new box wizard so only the users who care woudl go through it and others would have a quick expirience

[bastik-1001]

what we could do though would be to add a check box on the final page offering to open the new box wizard so only the users who care woudl go through it and others would have a quick expirience

This seems to be a good solution and gives users a great deal of control, whenever or not they want to configure the default box or simply start with the preset.

[DavidXanatos]

btw any suggestions what else we could put into the 1st start wizard?

[bastik-1001]

btw any suggestions what else we could put into the 1st start wizard?

There is nothing that jumps to mind, right away. Maybe someone else has something that is important to decide by the user. If there is too much to configure on the first wizard, it might scare people away. Sandboxie needs, and probably has good defaults, and the user can make changes, when the need arises or when the user feels like being experienced enough changing the options to suit their needs.

[Dyras]

@DavidXanatos
Personally, I think it might be worth considering asking the user which programs they want to sandbox on first install.

As it is now, you have to dig through menus to make Firefox/Edge/Chrome/VLC/whatever run in a Sandbox. This could be mitigated by straight up asking the user "Hey, we found these programs installed on your computer. Which ones do you want to sandbox?"

And then maybe use the default templates so that the web browsers can store files in the default location.

... If we actually want to make it more normie friendly, that is. I think the one thing that sets Sandboxie back is that it's not really plug and play.

[bastik-1001]

[...] Personally, I think it might be worth considering asking the user which programs they want to sandbox on first install.

As it is now, you have to dig through menus to make Firefox/Edge/Chrome/VLC/whatever run in a Sandbox. This could be mitigated by straight up asking the user "Hey, we found these programs installed on your computer. Which ones do you want to sandbox?" [...]

While I assume that they have some goal, when they are installing Sandboxie, like either isolating something they have installed, try some software they are unsure about, or some other purpose, the idea of helping them sounds good.

Maybe this could be another wizard, that also can be invoked by the 1st start wizard and the new box wizard. Like a link, "Assist me setting up software to run in a box. And the software wizard asks, "What do you want to do?"

• "Run some already installed software in a box." followed by a dialog to select the software, which might have been found, or the user has to select it via file browser.
• "Install software into a box." followed by a dialog to browse to the installer.
• "Open something in a box." followed by a dialog to browse what they want to open

Having a box selection dialog, either after or before they decide on the purpose.

"Do you want to force that software into the box?" for the already installed software and maybe also for other files.

• "Yes."
• "No.

Such a software wizard (or whatever it could be called) can be run as often as needed and avoids to invoke the 1st start wizard over and over again. It isn't needed in the box wizard, since it can be used independently.