[tor-bugs] #27604 [Applications/Tor Browser]: Relocating the Tor Browser directory is broken with Tor Browser 8

[Tor Bug Tracker & Wiki]

#27604: Relocating the Tor Browser directory is broken with Tor Browser 8
-------------------------------------------------+-------------------------
 Reporter:  gk                                   |          Owner:  tbb-
                                                 |  team
     Type:  defect                               |         Status:  new
 Priority:  Medium                               |      Milestone:
Component:  Applications/Tor Browser             |        Version:
 Severity:  Normal                               |     Resolution:
 Keywords:  tbb-8.0-issues, tbb-regression,      |  Actual Points:
  tbb-8.0.1-can, TorBrowserTeam201910            |
Parent ID:                                       |         Points:  0.5
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by mcs):

 This problem still exists with Tor Browser 9.0a8. After renaming the
 profile directory, HTTPS-E and NoScript are both broken. On macOS we had
 to remove the following three files in order to make things work again (I
 assume this is also true for Windows and Linux, although the file paths
 are different):
 {{{
 TorBrowser-Data/Browser/XXX.default/extensions.json
 TorBrowser-Data/Browser/Caches/XXX.default/startupCache/webext.sc.lz4
 TorBrowser-Data/Browser/XXX.default/addonStartup.json.lz4
 }}}
 Looking at the code, each is handled in a different place.

 For `extensions.json`, the solution described here should work:
 https://bugzilla.mozilla.org/show_bug.cgi?id=1429838#c11

 For `webext.sc.lz4`, we could use a similar solution: we could modify
 `_readData()` inside `components/extensions/ExtensionParent.jsm` to check
 extension paths and ignore the cached data if one or more files pointed to
 by the paths no longer exist.

 For `addonStartup.json.lz4`, we could again use a similar solution: we
 could modify `loadExtensionState()` inside
 `toolkit/mozapps/extensions/internal/XPIProvider.jsm` to check extension
 paths and ignore the cached data if paths have changed.

 All of the above said, it is too risky to fix this in Tor Browser 9.0.
 Maybe something for 9.5alpha?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/27604#comment:19>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online