Skip to content

Drop profile.default from our build scripts

Sould we drop profile.default from our build script?

As far as I can tell, you can launch Tor Browser with an empty Browser/TorBrowser/Data/Browser/ directory and the auto-created profile seems to be correct and contains NoScript. So why do we still pre-fill it with profile.default for new installs?

The advantage of not having profile.default is that we can ensure that all new profiles are in the same initial state. Which should help ensure that the first profile does not have any special status over newer profiles created through the UI (see tor-browser#43678 where this may become more prevalent) or replaced via about:support.

/cc @pierov @morgan @boklm

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information