Rip mozTCPSocket out of Tor Browser

In legacy/trac#18863 (moved) we disabled the usage of mozTCPSocket per preference. We might want to rip out that code as a defense in depth.

added component::applications/tor browser in Legacy / Trac owner::tbb-team in Legacy / Trac priority::medium in Legacy / Trac severity::normal in Legacy / Trac status::new in Legacy / Trac type::enhancement in Legacy / Trac labels

mentioned in issue legacy/trac#21625 (moved)

moved from legacy/trac#18866 (moved)

added Feature label and removed 1 deleted label

removed 1 deleted label

a quick look on searchfox seems to indicate mozTCPSocket is now hard-coded to only be available for system principals, which a quick look in the debugger seems to confirm. That said, nothing in the codebase seems to actually reference the exposed symbol except for tests, so there's nothing stopping us from writing a patch and ripping it out.

arthur

Yes, this pref [dom.mozTCPSocket.enabled] was removed in 1286530. I confirmed that navigator.mozTCPSocket is only exposed in chrome contexts

^ although that was 4 years ago

https://searchfox.org/mozilla-central/search?q=mozTCPSocket&path=&case=false&regexp=false

added First Contribution Icebox labels

added Roadmap::Future label

removed Icebox label

added Linkability label

added Task label and removed Feature label

removed Task label

added Feature label

added Uplift label

In fact, we could probably gate them behind the MOZ_PROXY_BYPASS_PROTECTION compile-time pref.

added Sponsor 131 label

added All Platforms label

added Apps::Priority::Low label

removed Uplift label

added Apps::Type::Chore label

added Apps::Impact::Low label