#32418: Torbrowser tells on every start, that it can't update although it is newest --------------------------------------+----------------------------------- Reporter: Yeti | Owner: tbb-team Type: defect | Status: needs_information Priority: Medium | Milestone: Component: Applications/Tor Browser | Version: Severity: Normal | Resolution: Keywords: tbb-update | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: --------------------------------------+-----------------------------------
Comment (by mcs): Revisiting this issue. We could provide a way for advanced users to disable updates through one of two approaches: 1. Reinstate support for the old `app.update.enabled` preference. This could be done by modifying the `disabledByPolicy()` function in `toolkit/mozapps/update/UpdateService.jsm`. 2. Turn support for enterprise policies back on (see #29916 and #30575) while removing support for reading policies from the Windows Registry and the macOS user defaults system. We would modify `toolkit/components/enterprisepolicies/EnterprisePolicies.js` to remove `WindowsGPOPoliciesProvider` and `macOSPoliciesProvider`. That would mean that policies would only work if they were added to a `distribution/policies.json` within the Tor Browser directory. See https://support.mozilla.org/en-US/kb/customizing-firefox-using- policiesjson Comments? Kathy and I have a slight preference for approach 2 because that would allow advanced users to use enterprise policy mechanism for other things too. Which method do other people prefer? -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32418#comment:9> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs