Tor Browser issueshttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues2020-09-28T15:51:23Zhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/33954Consider different approach for "2176: Rebrand Firefox to TorBrowser "2020-09-28T15:51:23ZAlex CatarineuConsider different approach for "2176: Rebrand Firefox to TorBrowser "The current patch replaces all occurrences of `branding/brand.ftl` with `branding/tor-browser-brand.ftl`. This means that many files are touched by the patch (increasing chances of rebase conflict), and whenever Firefox adds new instance...The current patch replaces all occurrences of `branding/brand.ftl` with `branding/tor-browser-brand.ftl`. This means that many files are touched by the patch (increasing chances of rebase conflict), and whenever Firefox adds new instances of `branding/brand.ftl` we need to modify the patch to also cover those.
I think we should try a different approach to keep all instances of `branding/brand.ftl` untouched, and do the `branding/brand.ftl` -> `branding/tor-browser-brand.ftl` remapping somewhere else, and just in a single place.
One way would be to force the Fluent `FileSource` that we register in torbutton to take precedence over any other source and rename `tor-browser-brand.ftl` to `brand.ftl`, to override Firefox one (including langpacks).
We probably would need to do this in [L10nRegistry.js](https://searchfox.org/mozilla-central/rev/3446310d6cc5c85cde16a82eccf560e9b71a3d44/intl/l10n/L10nRegistry.jsm#141), but I would need to investigate a bit more.Tor Browser: 10.0https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40646Revert #40475 and inherit upstream fix2021-12-20T11:07:48ZMatthew FinkelRevert #40475 and inherit upstream fixLanded as 754191343e929e2bf78f5597ee727231625d174bLanded as 754191343e929e2bf78f5597ee727231625d174bTor Browser: 11.0 Issues with previous releasehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/34319remove symlink support from the updater2023-05-13T09:51:57ZMark Smithremove symlink support from the updaterOur updater patch (legacy/trac#4234) adds support for handling symlinks during MAR file generation and in the updater itself. The original reason for adding this feature was to support meek's use of a second browser for its HTTP tunnel; ...Our updater patch (legacy/trac#4234) adds support for handling symlinks during MAR file generation and in the updater itself. The original reason for adding this feature was to support meek's use of a second browser for its HTTP tunnel; see legacy/trac#12647.
We no longer use symlinks on any platform. Kathy and I think we should remove the symlink portions of the legacy/trac#4234 patch (smaller patches == good).Sponsor 131 - Phase 3 - Major ESR 102 Migrationhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41842Remove the old removal logics from Torbutton2023-10-03T13:29:23ZPier Angelo VendrameRemove the old removal logics from Torbuttontorbutton@2dfa0e0c9cff7cfad93664e0b0b6cdc05b24b7f2 introduced some logic to remove old files (`$profile/cookies|protected-*.json`) that aren't used anymore.
However, after the 12.0 watershed, we don't need it for sure anymore.
Also, th...torbutton@2dfa0e0c9cff7cfad93664e0b0b6cdc05b24b7f2 introduced some logic to remove old files (`$profile/cookies|protected-*.json`) that aren't used anymore.
However, after the 12.0 watershed, we don't need it for sure anymore.
Also, there is a function to mess with preferences that we don't need anymore.
So, as part of the great torbutton cleanup, remove all of this.Pier Angelo VendramePier Angelo Vendramehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41346Handle delays for the tor process startup in TorConnect2024-03-26T08:58:42ZPier Angelo VendrameHandle delays for the tor process startup in TorConnectIf I understood correctly, `TorConnect` immediately switches from `Initial` to `Configuring`.
However, if the tor process takes a while to start, we should not switch immediately, but observe and wait for it to start.
This can be easil...If I understood correctly, `TorConnect` immediately switches from `Initial` to `Configuring`.
However, if the tor process takes a while to start, we should not switch immediately, but observe and wait for it to start.
This can be easily tested by setting `extensions.torlauncher.launch_delay`.https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/33172Start using a maintained version of osslsigncode for our authenticode signing2022-07-09T04:24:04ZGeorg KoppenStart using a maintained version of osslsigncode for our authenticode signing`osslsigncode` on SoureForge seems to be dead for a while now. It's worth switching to a maintained version, e.g. [mtrojnar's](https://github.com/mtrojnar/osslsigncode) one.`osslsigncode` on SoureForge seems to be dead for a while now. It's worth switching to a maintained version, e.g. [mtrojnar's](https://github.com/mtrojnar/osslsigncode) one.https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/32173Update signing infrastructure to work with Apple's notarization process2022-07-09T04:11:53ZGeorg KoppenUpdate signing infrastructure to work with Apple's notarization processWe have some working way of dealing with Apple's notarization requirement. We should now update our signing infrastructure with what we've learned so far.We have some working way of dealing with Apple's notarization requirement. We should now update our signing infrastructure with what we've learned so far.