Use NetworkLinkService instead of Moat for the internet test

henryrequested to merge
henry/tor-browser:network-link-service-internet-test-tb43462 into tor-browser-128.7.0esr-14.5-1

Merge Info

Issues

Resolves

Related

Merging

Target Branches

  • tor-browser - !fixups to tor-browser-specific commits, new features, security backports
  • base-browser and mullvad-browser - !fixups to base-browser-specific commits, new features to be shared with mullvad-browser, and security backports
    • ⚠️ IMPORTANT: Please list the base-browser-specific commits which need to be cherry-picked to the base-browser and mullvad-browser branches here

Target Channels

  • Alpha: esr128-14.5
  • Stable: esr128-14.0
  • Legacy: esr115-13.5

Backporting

Timeline

  • No Backport (preferred): patchset for the next major stable
  • Immediate: patchset needed as soon as possible (fixes CVEs, 0-days, etc)
  • Next Minor Stable Release: patchset that needs to be verified in nightly before backport
  • Eventually: patchset that needs to be verified in alpha before backport

(Optional) Justification

  • Security update: patchset contains a security fix (be sure to select the correct item in Timeline)
  • Censorship event: patchset enables censorship circumvention
  • Critical bug-fix: patchset fixes a bug in core-functionality
  • Consistency: patchset which would make development easier if it were in both the alpha and release branches; developer tools, build system changes, etc
  • Sponsor required: patchset required for sponsor
  • Localization: typos and other localization changes that should be also in the release branch
  • Other: please explain

Issue Tracking

Review

Request Reviewer

  • Request review from an applications developer depending on modified system:
    • NOTE: if the MR modifies multiple areas, please /cc all the relevant reviewers (since Gitlab only allows 1 reviewer)
    • accessibility : henry
    • android : clairehurst, dan
    • build system : boklm
    • extensions : ma1
    • firefox internals (XUL/JS/XPCOM) : jwilde, ma1
    • fonts : pierov
    • frontend (implementation) : henry
    • frontend (review) : donuts, morgan
    • localization : henry, pierov
    • macOS : clairehurst, dan
    • nightly builds : boklm
    • rebases/release-prep : dan, ma1, pierov, morgan
    • security : jwilde, ma1
    • signing : boklm, morgan
    • updater : pierov
    • windows : jwilde, morgan
    • misc/other : pierov, morgan

Change Description

We drop the Moat internet test and instead use NetworkLinkService to set TorConnect.internetStatus. This is used internally and by about:torconnect#connection.

In the latter case we can drop the "Test" button from the DOM.

How Tested

Used TorConnect.simulateOffline to test the bootstrap response to being offline.

Tested the status in about:torconnect#connection when switching off my wifi and back.

Unlike the Moat check, this won't respond to the internet being inaccessible for other reasons, such as your firewall or VPN being down. This is neither a net improvement or regression since the Moat check could falsely think you were offline if you blocked HTTPS, but not tor traffic.

I'm not sure how to test the response to linkStatusKnown being false. On most platforms this value only switches from false to true, but I'm not sure when this happens. On macOS there seems to be some mechanism to switch this back to false.

Edited by henry

Merge request reports