# Gateway
elif [ -e /usr/share/anon-gw-base-files/gateway ]; then
# Display alert that 'whonix-tor-disable' service flag is set and it will need to
# to manually unset if user wants to be able to boot with Tor enabled.
if [ -e /var/run/qubes-service/whonix-tor-disable ]; then
/usr/lib/qubes-whonix/alert tor-disabled /usr/lib/qubes-whonix/messages.yaml
exit 0
fi
## Check if Tor is disabled.
if grep "^#DisableNetwork 0$" /etc/tor/torrc; then
## Tor is disabled, therefore start whonix-setup-wizard in quick mode.
kdesudo whonix-setup-wizard quick
## Check if Tor is still disabled.
if grep "^#DisableNetwork 0$" /etc/tor/torrc ; then
true "Tor is still disabled, therefore take no action."
else
## Tor is enabled now, most likely the user enabled it using whonix-setup-wizard.
## When whonixcheck is automatically started at boot, while Tor is disabled
## in /etc/tor/torrc, whonixcheck exits silently.
## (whonixcheck does this because it is assumed, that in these cases Whonix
## Setup starts.) (Most likely happens at first boot.)
## If Tor has been enabled, restart whonixcheck daemon so whonixcheck will
## check Tor's bootstrap status among other things.
## Check if whonixcheck daemon is even running before attempting to
## restart it. This aids systems where whonixcheck is not installed
## or disabled by the user.
if sudo --non-interactive systemctl --no-pager status whonixcheck ; then
sudo --non-interactive systemctl --no-pager restart whonixcheck || true
fi
fi
fi
fi
… is no longer up to date. grep "^#DisableNetwork 0$" /etc/tor/torrc won’t work anymore in the age of torrc.d. I would like to get rid of the whole part.
The status file in /var/cache/whonix-setup-wizard/status-files/whonixsetup.skip qubes-whonix package is currently preventing autostart of whonix-setup-wizard in Qubes-Whonix. Therefore,
/var/cache/whonix-setup-wizard/status-files/whonixsetup.skip should be removed from qubes-whonix package
therefore whonix-legacy package should create /var/cache/whonix-setup-wizard/status-files/whonixsetup.done so whonix-setup-wizard will not autostart for Qubes-Whonix 13 → Qubes-Whonix 14 upgraded systems
Now, all the things left in whonix-setup-wizard are:
a not elegant integration with anon-connection-wizard
locale_settings
bootstrap of whonixcheck script
I am wondering if we still use whonix-setup-wizard as an unified place to present user all the configurations? If so, I can help to see how we can elegantly integrate it with other actually standalone applications (anon-connection-wizard, whonix-repository-wizard for example).
Regarding whonix-setup-wizard, the GUI with the big button Launch Anon Connection Wizard seems to be redundant. The script is left whit too possible arguments.
Why not the following:
if argument = setup → run anon-connection-wizard directly, run whonixcheck on completion.
if argument = locale_settings → run kcmshell, and possibly run whonixcheck on completion.
whonix-setup-wizard code could be stripped down to a minimum.
Should we use /usr/local/etc/torrc.d/40_anon_connection_wizard.torrc instead? Otherwise, /etc/torrc.d/40_anon_connection_wizard.torrc is still not persistent in templateBased VMs?