The Tor Project issueshttps://gitlab.torproject.org/groups/tpo/-/issues2022-11-09T08:44:13Zhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41251Tor binary we build seems to not getting picked up in nightly builds2022-11-09T08:44:13ZGeorg KoppenTor binary we build seems to not getting picked up in nightly buildsWe build Tor for Android now ourselves thanks to the fix for legacy/trac#28766. But unfortunately it seems at least as it is not picked up yet, despite legacy/trac#32993 claiming so. I stumbled across this when testing a fix for legacy/t...We build Tor for Android now ourselves thanks to the fix for legacy/trac#28766. But unfortunately it seems at least as it is not picked up yet, despite legacy/trac#32993 claiming so. I stumbled across this when testing a fix for legacy/trac#32027. The branch has all patches for legacy/trac#28704 and children but it's still shown that we use the Tor we've been bundling so far but not the one we compile.Sponsor 131 - Phase 3 - Major ESR 102 MigrationDan BallardDan Ballardhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41150Review Mozilla 1753302: Make WebGPU accessible via OffscreenCanvas2022-10-18T20:38:44ZrichardReview Mozilla 1753302: Make WebGPU accessible via OffscreenCanvas## https://bugzilla.mozilla.org/show_bug.cgi?id=1753302
More offscreen canvas fingerprinting fun to worry about
related: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41135## https://bugzilla.mozilla.org/show_bug.cgi?id=1753302
More offscreen canvas fingerprinting fun to worry about
related: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41135Sponsor 131 - Phase 3 - Major ESR 102 MigrationDan BallardDan Ballardhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41149Review Mozilla 1762576: Firefox is not allowing Symantec DLP to inject DLL i...2022-10-21T20:23:58ZrichardReview Mozilla 1762576: Firefox is not allowing Symantec DLP to inject DLL into the browser for Data Loss Prevention software## https://bugzilla.mozilla.org/show_bug.cgi?id=1762576
Here's a thought, let's not let random processes inject dlls into tor-browser (to be clear I propose we revert / disable this funcitonality)## https://bugzilla.mozilla.org/show_bug.cgi?id=1762576
Here's a thought, let's not let random processes inject dlls into tor-browser (to be clear I propose we revert / disable this funcitonality)Sponsor 131 - Phase 3 - Major ESR 102 MigrationDan BallardDan Ballardhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41147Review Mozilla 1766401: Add a Nimbus feature to enable TCP by default for ph...2022-10-25T22:11:45ZrichardReview Mozilla 1766401: Add a Nimbus feature to enable TCP by default for phase 2## https://bugzilla.mozilla.org/show_bug.cgi?id=1766401
No idea what this does but it messes with cookies and networking so we should take a look## https://bugzilla.mozilla.org/show_bug.cgi?id=1766401
No idea what this does but it messes with cookies and networking so we should take a lookSponsor 131 - Phase 3 - Major ESR 102 Migrationma1ma1https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41134Review Mozilla 1749501: "Use system proxy settings" no longer uses all define...2022-10-23T23:38:48ZrichardReview Mozilla 1749501: "Use system proxy settings" no longer uses all defined exceptionsWe need to make sure this change is interacting correctly with our proxy bypass expections. If there's any fixes required they should be gated behind MOZ_PROXY_BYPASS_PROTECTION and uplifted.We need to make sure this change is interacting correctly with our proxy bypass expections. If there's any fixes required they should be gated behind MOZ_PROXY_BYPASS_PROTECTION and uplifted.Sponsor 131 - Phase 3 - Major ESR 102 Migrationma1ma1https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41128Review Mozilla 1734331: Upgrade toolchains to macosx-sdk 11.02022-09-02T09:02:45ZrichardReview Mozilla 1734331: Upgrade toolchains to macosx-sdk 11.0## https://bugzilla.mozilla.org/show_bug.cgi?id=1734331
Not a security issue for of an FYI, but it seems like we will also need to upgrade to the 11.0 sdk for macOS arm builds## https://bugzilla.mozilla.org/show_bug.cgi?id=1734331
Not a security issue for of an FYI, but it seems like we will also need to upgrade to the 11.0 sdk for macOS arm buildsSponsor 131 - Phase 3 - Major ESR 102 Migrationboklmboklmhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41125Review Mozilla 1732792: retry polling requests without proxy2022-10-18T15:21:15ZrichardReview Mozilla 1732792: retry polling requests without proxyWe should not do anything without the proxy, (if it isn't already) we should gate this feature behind MOZ_PROXY_BYPASS_PROTECTION and uplift.We should not do anything without the proxy, (if it isn't already) we should gate this feature behind MOZ_PROXY_BYPASS_PROTECTION and uplift.Sponsor 131 - Phase 3 - Major ESR 102 MigrationDan BallardDan Ballardhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41117Review Mozilla 1512851: Add Share Menu to File Menu on macOS2023-04-19T19:52:24ZrichardReview Mozilla 1512851: Add Share Menu to File Menu on macOS## https://bugzilla.mozilla.org/show_bug.cgi?id=1512851
Adds a File > Share menu on macOS. Seems like a great linkability vector.
@duncan: can you verify this menu appears in the esr102-based alpha?
@pierov: do you have an opinion on w...## https://bugzilla.mozilla.org/show_bug.cgi?id=1512851
Adds a File > Share menu on macOS. Seems like a great linkability vector.
@duncan: can you verify this menu appears in the esr102-based alpha?
@pierov: do you have an opinion on whether this should be disabled in tor-browser or base-browser
@dan: I'd like you to write w/e patch is required for disabling this.Sponsor 131 - Phase 3 - Major ESR 102 MigrationDan BallardDan Ballardhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40587Migrate tor-browser-build configs from gitolite to gitlab repos2022-10-14T14:38:50ZrichardMigrate tor-browser-build configs from gitolite to gitlab reposGitolite is going away, we should migrate our build configs to using the gitlab code mirrors where appropriate.Gitolite is going away, we should migrate our build configs to using the gitlab code mirrors where appropriate.Sponsor 131 - Phase 3 - Major ESR 102 Migrationrichardrichardhttps://gitlab.torproject.org/tpo/applications/team/-/issues/12Delete various master branches after automated build/testing scripts are updated2022-09-23T22:56:32ZrichardDelete various master branches after automated build/testing scripts are updated`main` branches added to the following for 12.0a1
* [x] Tor Browser Build
- [x] delete `master` on gitlolite
- [x] delete `master` on gitlab
- [x] block `master` on gitlab
* [x] RBM
- [x] delete `master` on gitlolite
- [x] de...`main` branches added to the following for 12.0a1
* [x] Tor Browser Build
- [x] delete `master` on gitlolite
- [x] delete `master` on gitlab
- [x] block `master` on gitlab
* [x] RBM
- [x] delete `master` on gitlolite
- [x] delete `master` on gitlab
- [x] block `master` on gitlab
* [x] Torbutton
- [x] delete `master` on gitlolite
- [x] delete `master` on gitlab
- [x] block `master` on gitlab
* [x] Tor Launcher
- [x] delete `master` on gitlolite
- [x] delete `master` on gitlab
- [x] block `master` on gitlab
* [x] Tor Android Service
- [x] delete `master` on gitlolite
- [x] delete `master` on gitlab
- [x] block `master` on gitlab
* [x] Tor Browser Bundle Testsuite
- [x] delete `master` on gitlolite
- [x] delete `master` on gitlab
- [x] block `master` on gitlab
* [x] Tor Browser Spec
- [x] delete `master` on gitlolite
- [x] delete `master` on gitlab
- [x] block `master` on gitlab
In theory we should be done with `torbutton` and `tor-launcher` after 12.0 stable is released but we'll see.Sponsor 131 - Phase 3 - Major ESR 102 Migrationrichardrichardhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41018ESR102 windows add Consolas to whitelist2022-08-09T12:02:12ZThorinESR102 windows add Consolas to whitelistWe should add Consolas to Windows whitelist in ESR102 (flag day)
* FF99 changed a default font - consolas instead of courier new
* https://bugzilla.mozilla.org/show_bug.cgi?id=713680
* https://bugzilla.mozilla.org/show_bug.cgi?id=16...We should add Consolas to Windows whitelist in ESR102 (flag day)
* FF99 changed a default font - consolas instead of courier new
* https://bugzilla.mozilla.org/show_bug.cgi?id=713680
* https://bugzilla.mozilla.org/show_bug.cgi?id=1607913
attn: @pierov
label: FFR102-esrSponsor 131 - Phase 3 - Major ESR 102 MigrationPier Angelo VendramePier Angelo Vendramehttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40464go 1.18 fails to build on macOS2022-10-20T19:59:31Zrichardgo 1.18 fails to build on macOS@pierov ran into this issue while we were attempting to build alpha 11.5a8:
```
Opening log file: Thu Mar 17 19:08:27 2022
Starting build (script: build): 2022-03-17 19:08:28
# golang.org/x/sys/unix
unix/zsyscall_darwin_amd64.go:28:3: /...@pierov ran into this issue while we were attempting to build alpha 11.5a8:
```
Opening log file: Thu Mar 17 19:08:27 2022
Starting build (script: build): 2022-03-17 19:08:28
# golang.org/x/sys/unix
unix/zsyscall_darwin_amd64.go:28:3: //go:linkname must refer to declared function or variable
unix/zsyscall_darwin_amd64.go:43:3: //go:linkname must refer to declared function or variable
unix/zsyscall_darwin_amd64.go:59:3: //go:linkname must refer to declared function or variable
unix/zsyscall_darwin_amd64.go:75:3: //go:linkname must refer to declared function or variable
unix/zsyscall_darwin_amd64.go:90:3: //go:linkname must refer to declared function or variable
unix/zsyscall_darwin_amd64.go:105:3: //go:linkname must refer to declared function or variable
unix/zsyscall_darwin_amd64.go:121:3: //go:linkname must refer to declared function or variable
unix/zsyscall_darwin_amd64.go:136:3: //go:linkname must refer to declared function or variable
unix/zsyscall_darwin_amd64.go:151:3: //go:linkname must refer to declared function or variable
unix/zsyscall_darwin_amd64.go:166:3: //go:linkname must refer to declared function or variable
unix/zsyscall_darwin_amd64.go:166:3: too many errors
Finishing build (script: build): 2022-03-17 19:08:33
Build time: 0 hours 0 minutes and 5 seconds
```
Some initial googling points us to: https://stackoverflow.com/questions/71507321/go-upgrade-to-1-18-go-build-run-with-error-my-system-is-mac-12
In the meantime I've reverted the go update on the alpha branch until we can investigate/implement a fix.Sponsor 131 - Phase 3 - Major ESR 102 MigrationDan BallardDan Ballardhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40439Create universal x86-64/arm64 mac builds2022-12-04T17:29:14ZboklmCreate universal x86-64/arm64 mac buildsIn #40158 we add support for macOS aarch64 builds. However, to avoid doubling the space used by macOS builds we should create universal x86-64/arm64 dmg files.
The tickets on mozilla side are:
* https://bugzilla.mozilla.org/show_bug.cgi...In #40158 we add support for macOS aarch64 builds. However, to avoid doubling the space used by macOS builds we should create universal x86-64/arm64 dmg files.
The tickets on mozilla side are:
* https://bugzilla.mozilla.org/show_bug.cgi?id=1675740
* https://bugzilla.mozilla.org/show_bug.cgi?id=1675384
I think the scripts from Mozilla we can use for that are:
* taskcluster/scripts/misc/unify.sh
* toolkit/mozapps/installer/unify.pySponsor 131 - Phase 3 - Major ESR 102 Migrationboklmboklmhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40790Remove tor-launcher uninstall logic in XPIProvider.jsm2022-08-09T12:01:23ZPier Angelo VendrameRemove tor-launcher uninstall logic in XPIProvider.jsm#28044 (65de30eae9d7493e1d54edde47bc1422fba0fe0e for 91.5) still includes the checks for the Tor Launcher extension, and uninstalls it, if present.
The extension has long gone, as well as compatibility with legacy extensions in Firefox,...#28044 (65de30eae9d7493e1d54edde47bc1422fba0fe0e for 91.5) still includes the checks for the Tor Launcher extension, and uninstalls it, if present.
The extension has long gone, as well as compatibility with legacy extensions in Firefox, so we may remove this part from our patch set.Sponsor 131 - Phase 3 - Major ESR 102 MigrationPier Angelo VendramePier Angelo Vendramehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40751Drop libmdns patch (the one for #18821)2022-08-09T12:00:37ZGeorg KoppenDrop libmdns patch (the one for #18821)Starting with Firefox 97 this is not needed anymore. See: https://bugzilla.mozilla.org/show_bug.cgi?id=1432983.Starting with Firefox 97 this is not needed anymore. See: https://bugzilla.mozilla.org/show_bug.cgi?id=1432983.Sponsor 131 - Phase 3 - Major ESR 102 MigrationPier Angelo VendramePier Angelo Vendramehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40745Switch away from MessageChannel.jsm2022-08-09T12:00:42ZGeorg KoppenSwitch away from MessageChannel.jsmMozilla uses the so-called actor messaging now which made the logic in MessageChannel.jsm obsolete. (see: #40741 for details) We should look into how we can use that new model for talking to NoScript asap.Mozilla uses the so-called actor messaging now which made the logic in MessageChannel.jsm obsolete. (see: #40741 for details) We should look into how we can use that new model for talking to NoScript asap.Sponsor 131 - Phase 3 - Major ESR 102 MigrationPier Angelo VendramePier Angelo Vendramehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40743dom.securecontext.allowlist_onions2022-08-09T12:02:33ZThorindom.securecontext.allowlist_onions[1744006](https://bugzilla.mozilla.org/show_bug.cgi?id=1744006) rename ....
might as well add it now next to the old pref in overrides so no-one forgets come next ESR
```js
pref("dom.securecontext.allowlist_onions", true); // FF97+ 1744...[1744006](https://bugzilla.mozilla.org/show_bug.cgi?id=1744006) rename ....
might as well add it now next to the old pref in overrides so no-one forgets come next ESR
```js
pref("dom.securecontext.allowlist_onions", true); // FF97+ 1744006 renamed from whitelist
```
@gkSponsor 131 - Phase 3 - Major ESR 102 MigrationPier Angelo VendramePier Angelo Vendramehttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40251Clear obsolete prefs after torbutton!272022-10-24T20:16:51ZAlex CatarineuClear obsolete prefs after torbutton!27Sponsor 131 - Phase 3 - Major ESR 102 Migrationrichardrichardhttps://gitlab.torproject.org/tpo/applications/tor-browser-build/-/issues/40158Tor Browser for macOS aarch642022-11-21T02:25:12ZMatthew FinkelTor Browser for macOS aarch64Mozilla Firefox tracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1648496
Tor tracking bug: tpo/core/tor#40198Mozilla Firefox tracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1648496
Tor tracking bug: tpo/core/tor#40198Sponsor 131 - Phase 3 - Major ESR 102 Migrationboklmboklmhttps://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40065use an appropriate value for network.http.sendOriginHeader2022-10-31T15:44:01ZMark Smithuse an appropriate value for network.http.sendOriginHeaderFrom #33534: In Firefox 70, the `network.http.sendOriginHeader` pref value was changed from `0` (never send Origin header) to `2` (always send). What value should Tor Browser use?
https://bugzilla.mozilla.org/show_bug.cgi?id=1424076 \
"...From #33534: In Firefox 70, the `network.http.sendOriginHeader` pref value was changed from `0` (never send Origin header) to `2` (always send). What value should Tor Browser use?
https://bugzilla.mozilla.org/show_bug.cgi?id=1424076 \
"Enable network.http.sendOriginHeader by default"Sponsor 131 - Phase 3 - Major ESR 102 Migrationma1ma1