Before reordering patches, we used to keep the Tor-related patches
(torbutton and tor-launcher) at the beginning.
After that issue, we decided to move them towards the end.

In addition to that, we have decided to move Tor Browser-only
preferences there, too, to make Base Browser-only fixups easier to
apply.

Mike Perry authored 11 years ago and Pier Angelo Vendrame committed 1 year ago

This hack directly includes our preference changes in omni.ja.

Bug 18292: Staged updates fail on Windows

Temporarily disable staged updates on Windows.

Bug 18297: Use separate Noto JP,KR,SC,TC fonts

Bug 23404: Add Noto Sans Buginese to the macOS whitelist

Bug 23745: Set dom.indexedDB.enabled = true

Bug 13575: Disable randomised Firefox HTTP cache decay user tests.
(Fernando Fernandez Mancera <ffmancera@riseup.net>)

Bug 17252: Enable session identifiers with FPI

Session tickets and session identifiers were isolated
by OriginAttributes, so we can re-enable them by
allowing the default value (true) of
"security.ssl.disable_session_identifiers".

The pref "security.enable_tls_session_tickets" is obsolete
(removed in https://bugzilla.mozilla.org/917049)

Bug 14952: Enable http/2 and AltSvc

In Firefox, SPDY/HTTP2 now uses Origin Attributes for
isolation of connections, push streams, origin frames, etc.
That means we get first-party isolation provided
"privacy.firstparty.isolate" is true. So in this patch, we
stop overriding "network.http.spdy.enabled" and
"network.http.spdy.enabled.http2".

Alternate Services also use Origin Attributes for isolation.
So we stop overriding
"network.http.altsvc.enabled" and "network.http.altsvc.oe"
as well.

(All 4 of the abovementioned "network.http.*" prefs adopt
Firefox 60ESR's default value of true.)

However, we want to disable HTTP/2 push for now, so we
set "network.http.spdy.allow-push" to false.

"network.http.spdy.enabled.http2draft" was removed in Bug 1132357.
"network.http.sped.enabled.v2" was removed in Bug 912550.
"network.http.sped.enabled.v3" was removed in Bug 1097944.
"network.http.sped.enabled.v3-1" was removed in Bug 1248197.

Bug 26114: addons.mozilla.org is not special
* Don't expose navigator.mozAddonManager on any site
* Don't block NoScript from modifying addons.mozilla.org or other sites

Enable ReaderView mode again (#27281).

Bug 29916: Make sure enterprise policies are disabled

Bug 2874: Block Components.interfaces from content

Bug 26146: Spoof HTTP User-Agent header for desktop platforms

In Tor Browser 8.0, the OS was revealed in both the HTTP User-Agent
header and to JavaScript code via navigator.userAgent. To avoid
leaking the OS inside each HTTP request (which many web servers
log), always use the Windows 7 OS value in the desktop User-Agent
header. We continue to allow access to the actual OS via JavaScript,
since doing so improves compatibility with web applications such
as GitHub and Google Docs.

Bug 12885: Windows Jump Lists fail for Tor Browser

Jumplist entries are stored in a binary file in:
  %APPDATA%\\Microsoft\Windows\Recent\CustomDestinations\
and has a name in the form
  [a-f0-9]+.customDestinations-ms

The hex at the front is unique per app, and is ultimately derived from
something called the 'App User Model ID' (AUMID) via some unknown
hashing method. The AUMID is provided as a key when programmatically
creating, updating, and deleting a jumplist. The default behaviour in
firefox is for the installer to define an AUMID for an app, and save it
in the registry so that the jumplist data can be removed by the
uninstaller.

However, the Tor Browser does not set this (or any other) regkey during
installation, so this codepath fails and the app's AUMID is left
undefined. As a result the app's AUMID ends up being defined by
windows, but unknowable by Tor Browser. This unknown AUMID is used to
create and modify the jumplist, but the delete API requires that we
provide the app's AUMID explicitly. Since we don't know what the AUMID
is (since the expected regkey where it is normally stored does not
exist) jumplist deletion will fail and we will leave behind a mostly
empty customDestinations-ms file. The name of the file is derived from
the binary path, so an enterprising person could reverse engineer how
that hex name is calculated, and generate the name for Tor Browser's
default Desktop installation path to determine whether a person had
used Tor Browser in the past.

The 'taskbar.grouping.useprofile' option that is enabled by this patch
works around this AUMID problem by having firefox.exe create it's own
AUMID based on the profile path (rather than looking for a regkey). This
way, if a user goes in and enables and disables jumplist entries, the
backing store is properly deleted.

Unfortunately, all windows users currently have this file lurking in
the above mentioned directory and this patch will not remove it since it
was created with an unknown AUMID. However, another patch could be
written which goes to that directory and deletes any item containing the
'Tor Browser' string.  See bug 28996.

Bug 30845: Make sure default themes and other internal extensions are enabled

Bug 28896: Enable extensions in private browsing by default

Bug 31065: Explicitly allow proxying localhost

Bug 31598: Enable letterboxing

Disable Presentation API everywhere

Bug 21549 - Use Firefox's WASM default pref. It is disabled at safer
security levels.

Bug 32321: Disable Mozilla's MitM pings

Bug 19890: Disable installation of system addons

By setting the URL to "" we make sure that already installed system
addons get deleted as well.

Bug 22548: Firefox downgrades VP9 videos to VP8.

On systems where H.264 is not available or no HWA, VP9 is preferred. But in Tor
Browser 7.0 all youtube videos are degraded to VP8.

This behaviour can be turned off by setting media.benchmark.vp9.threshold to 0.
All clients will get better experience and lower traffic, beause TBB doesn't
use "Use hardware acceleration when available".

Bug 25741 - TBA: Add mobile-override of 000-tor-browser prefs

Bug 16441: Suppress "Reset Tor Browser" prompt.

Bug 29120: Use the in-memory media cache and increase its maximum size.

Bug 33697: use old search config based on list.json

Bug 33855: Ensure that site-specific browser mode is disabled.

Bug 30682: Disable Intermediate CA Preloading.

Bug 40061: Omit the Windows default browser agent from the build

Bug 40322: Consider disabling network.connectivity-service.enabled

Bug 40408: Disallow SVG Context Paint in all web content

Bug 40308: Disable network partitioning until we evaluate dFPI

Bug 40322: Consider disabling network.connectivity-service.enabled

Bug 40383: Disable dom.enable_event_timing

Bug 40423: Disable http/3

Bug 40177: Update prefs for Fx91esr

Bug 40700: Disable addons and features recommendations

Bug 40682: Disable network.proxy.allow_bypass

Bug 40736: Disable third-party cookies in PBM

Bug 19850: Enabled HTTPS-Only by default

Bug 40912: Hide the screenshot menu

Bug 41292: Disable moreFromMozilla in preferences page

Bug 40057: Ensure the CSS4 system colors are not a fingerprinting vector

Bug 24686: Set network.http.tailing.enabled to true

Bug 40183: Disable TLS ciphersuites using SHA-1

Bug 40783: Review 000-tor-browser.js and 001-base-profile.js for 102

We reviewed all the preferences we set for 102, and remove a few old
ones. See the description of that issue to see all the preferences we
believed were still valid for 102, and some brief description for the
reasons to keep them.

Differential Revision: https://phabricator.services.mozilla.com/D174335

Setting a timeout on the download means we can retry if the connection
hangs, instead of sitting around idle until the task itself hits its
maxRunTime.

Differential Revision: https://phabricator.services.mozilla.com/D173287

Bug 1821513 - patch mercurial debian package to make http.timeout option work r=releng-reviewers,bhearsum a=release

Cherry-pick from https://www.mercurial-scm.org/repo/hg/rev/3bb7c56e8fe6

Differential Revision: https://phabricator.services.mozilla.com/D173274

Bug 1824368: update known hosts file in parter repack docker image for github host key change r=releng-reviewers,jlorenzo a=release DONTBUILD

This adds the new RSA key from https://github.blog/2023-03-23-we-updated-our-rsa-ssh-host-key/, as well as the existing ed25519 keys (which I got from loading the partner repack image locally, and running `ssh github.com`).

Differential Revision: https://phabricator.services.mozilla.com/D173527

Backed out changeset 3e15a0e2be47 (bug 1799684) to avoid avoid conflicts
over the firefox-esr-next-langpack-latest-ssl bouncer alias when the
next ESR branch starts.

Differential Revision: https://phabricator.services.mozilla.com/D170086

Differential Revision: https://phabricator.services.mozilla.com/D169936

Differential Revision: https://phabricator.services.mozilla.com/D169779

I've seen the max hit a few times in the last couple of weeks; may as well bump it to avoid rerun friction.

Differential Revision: https://phabricator.services.mozilla.com/D164940

Differential Revision: https://phabricator.services.mozilla.com/D169741

Bug 1799684 - create the firefox-esr-next-langpack-latest-ssl bouncer alias with 102.8.0esr. r=gbrown,releng-reviewers, a=release

Creating the bouncer alias now means we don't have to wait until
115.0esr is shipped before adding it to bouncer-check.

This patch should land on esr102 only, and should get backed out after
102.8.0esr ships.

Differential Revision: https://phabricator.services.mozilla.com/D168798

Bug 1814418 - don't include android/geckoview builds in esr staging releases. r=releng-reviewers,gbrown a=pascalc

Instead of excluding android builds based on the `project` parameter, use
`release_type`, which is properly set to e.g. `esr102` by `mach try release`.

Differential Revision: https://phabricator.services.mozilla.com/D168563

Differential Revision: https://phabricator.services.mozilla.com/D167538

Bug 1811287 - Change repo-update reviewer to release-managers group. r=releng-reviewers,bhearsum a=NPOTB DONTBUILD

Differential Revision: https://phabricator.services.mozilla.com/D167278

This is an "uplift" of the patches that have landed on central and made / are
making their way down to release.

By pointing all aliases to GCP pools, I can avoid rebasing dozens of commits
and dealing with the inevitable merge conflicts.

Differential Revision: https://phabricator.services.mozilla.com/D164850

Differential Revision: https://phabricator.services.mozilla.com/D162694

Differential Revision: https://phabricator.services.mozilla.com/D161188

Bug 1793923 - stop pinning the hg.mozilla.org certificate in docker-worker tasks. r=releng-reviewers,gabriel a=release DONTBUILD

This way hg can verify that the cert chains to a trusted root CA, and we
don't have to pin it by fingerprint.

Differential Revision: https://phabricator.services.mozilla.com/D158748

Differential Revision: https://phabricator.services.mozilla.com/D158185

Differential Revision: https://phabricator.services.mozilla.com/D158018

Differential Revision: https://phabricator.services.mozilla.com/D156973

Differential Revision: https://phabricator.services.mozilla.com/D156971

Differential Revision: https://phabricator.services.mozilla.com/D155823

Differential Revision: https://phabricator.services.mozilla.com/D153734

Bug 1770636 - Fix StartupWMClass of flatpak package to match actually-used WMClass. r=jhorak, a=dmeehan

Pending further changes iff we want to do them (like comment 5), this is the
right thing to do.

I'm not a fan of comment 5 since in the past I've been bitten by Wayland
compositors not comparing stuff case-insensitively, so making everything
lowercase is probably simpler.

Differential Revision: https://phabricator.services.mozilla.com/D149911

Bug 1777521 - set firefox-esr-next-msix-latest-ssl bouncer alias on esr102. r=gbrown, a=dmeehan DONTBUILD

Differential Revision: https://phabricator.services.mozilla.com/D150761

- Because we don't have a native arm64 mac one, alias the x86_64 one.
- Because we always compress with zstd, don't pretend the main script
  has any power on the compression (which was wrong for Windows).

Differential Revision: https://phabricator.services.mozilla.com/D149204

Add build_platform so that the esr android filter will work.
https://searchfox.org/mozilla-central/rev/cc98a15c7327d742d283cddddde712a8a3165006/taskcluster/gecko_taskgraph/target_tasks.py#578-582

Differential Revision: https://phabricator.services.mozilla.com/D149791

Instead of pretending we're merging from release, just apply the
version bumps / replacements on the current state of the esr tree.

Differential Revision: https://phabricator.services.mozilla.com/D149747

Differential Revision: https://phabricator.services.mozilla.com/D148618

Bug 1570598 turned the windows gn binary into a 64-bits executable.
Reflect that in the toolchain and script names.

Differential Revision: https://phabricator.services.mozilla.com/D148617

Differential Revision: https://phabricator.services.mozilla.com/D147106

Bug 1771269 - Build local toolchains on integration+release rather than trunk. r=taskgraph-reviewers,ahal

In rare cases (but which do happen), some change lands on release
branches that invalidates the local toolchain hashes. In those cases,
the local toolchains are currently not produced unless something else
depends on them, which leaves bootstrapping broken on those branches.

Because setting the right set of `run-on-projects` is manual and
error-prone, it's simpler to simply leave it to the taskgraph code
to set it properly for tasks with the `local-toolchain` attribute.

Differential Revision: https://phabricator.services.mozilla.com/D147473