Long Wiki Edits Thread

[0brand]

@Patrick

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/

This biggest issue is flip-flopping between SecBrowser… Tor Browser, torbrowser and Tor Browswer without Tor… in the documentation. It was difficult for me to decide which term to use in some areas. It would likely be confusing for end users as well. Even more so.

@Patrick

In result users would not have to confusingly type qvm-run <appvm_name> torbrowser and could use qvm-run <appvm_name> secbrowser instead.

I didn’t catch this one. Users might think they are starting Tor Browser. Would be worth the effort.

@Patrick

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 / secbrowser would 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.)

All of this would make SecBrowser more of a standalone Browser. Meaning not always over shadowed by Tor Browser. Thats the biggest reason why Tor Browser without Tor never caught on imo. SecBrowser needs to be its own Secure Browser. (rebranding) Kinda like Whonix is based on Debian but its not Debian. Actually its in reverse, anonymity focused → security focused.

Changing the name would be very helpfull. Meaning when SecBrowser starts up you see SecBrowser not Tor Browser.