Nitpicking on myself, on something which couldn’t be documented better since the source code for that does not exist yet. Perhaps the following terms are confusing…?
update-torbrowsertorbrowser/rw/config/torbrowser.d/
All of that could be changed… Wrappers could be added with ease.
-
update-torbrowser->update-secbrowser -
torbrowser->secbrowser -
/rw/config/torbrowser.d/->/usr/local/etc/torbrowser.d/->/usr/local/etc/secbrowser.d/
For example /usr/bin/secbrowser (not for documentation, I could add this to the source code very soon):
#/bin/bash
torbrowser --clearnet "$@"
In result users would not have to confusingly type qvm-run <appvm_name> torbrowser and could use qvm-run <appvm_name> secbrowser instead.
Also availability of /usr/bin/secbrowser would allow us to add another, dedicated .desktop file, i.e. start menu entry.
- That start menu entry would be hidden (never visible by default) to users inside Whonix
- And users starting the Tor Browser start menu entry while
tb_clearnet=true/--clearnet/secbrowserwould be informed automagically that this is not possible (unless they remove the file that was created to protect from that). ""Clearnet marker file exists and trying to start without --clearnet. Aborted. A Tor Browser that was previously started with --clearnet should not be started without --clearnet."(Will improve that error message.)