Would be cool but seems difficult. I wouldn’t know. A rebrand would be good. We can see how far we get and then create feature requests upstream, see how they like the project once it stabilized a bit.
tb-updater package is still very Tor Browser focused in source code. The main script is /usr/bin/update-torbrowser and the other scripts (update-i2pbrowser / download-secbrowser) just wrap around it. A major refactoring would be worthwhile but also a lot work. The shared code makes up most and secbrowser specific code is very, very little actually, so not sure if justified to have a separate package. Also under consideration is merging tb-updater and tb-starter package and then rename to tpo-downloader (tpo-downloader because in past support for downloading (the now deprecated) Tor Messenger was planned and looked simple enough to implement) or something else?
Yeah it has a nice ring to it. The only relevant result using this name is some ancient browser by a company named “Tropical software”. Their domain seems out of order with an offer to buy it.
Does our naming fall under Whonix trademark protection?
These prefs have to be hard coded. Even with when added to user.js the values keep getting reset after vm restart. I’ll start going through the files in tb profile.default next
Let’s draft a feature request to be posted at trac.torproject.org. In my experience, the better any bug report / feature request is written, and then less [Whonix] specific it is, the better the chances of seing it implemented one day. On the other hand, the more discussion for clarification what it’s even about and reasoning why or off-topic deflection, the lower the chances anything ever is going to change.
Might edit this post. Feel free to edit it was a moderator / admin since the history feature to track changes is really neat.
subject:
document prefs / settings to set security slider level
content:
Could you please document how Tor Browser security level can be set via an prefs so we can give Whonix users an option to have more protection by default.
I’ve tried to start with a fresh installed Tor Browser profile, but it under git version control, start Tor Browser, change the setting and then see how file Browser/TorBrowser/Data/Browser/profile.default/prefs.js changed to then have a clue how to emulate to set these in Browser/TorBrowser/Data/Browser/profile.default/user.js.
By doing so, the security slider might show being set to maximum, however without the actual changes that the security slider would apply such as enabling noscript globally by default for all websites.
WordPress › Setup Configuration File - look how Tor Browser did the rebrand and see if if it is feasible for us too (hopefully without recompilation - not feasible)
I doubt this would be done just for Whonix devs/users. This would somehow have to benefit everyone.
Most requests are denied because they somehow degrade anonymity for everyone. Since they hardcoded these prefs(?) they don’t want Tor Browser users changing them around. Maybe the best approach is to upfront with them on the reason for doing this. Take Whonix out of the equation. While non for anonymity make sure they know Whonix devs have already completed a lot of work on this.
SecBrowser
Would be useful to everyone (everyone needs an security focused clearnet browser)
Its a good start. It will take some time to get it just right.
When SecBrowser is started, the about:tor tab opens and the focus is taken off the SecBrowser landing page. I restarted SecBrowser and the same thing happened.There has to be a way to fix this.
I have a new branding idea. Currently there is SecBrowser, Hardended Debian based OS and maybe more apps hardened by Whonix developers. We could use “Sec” as the brand for the OS and apps that are hardened. For example:
Ive been experimenting with pass-qubes in SecBrowser. I don’t think it would be an worse for fingerprinting than the current method (passwords stored in SecBrowser) but would be less attack surface.