Open K4sum1 opened 11 months ago
Some telemetry settings I found over the years, there may be more
media.wmf.deblacklisting-for-telemetry-in-gpu-process browser.ping-centre.telemetry toolkit.telemetry.archive.enabled toolkit.telemetry.bhrPing.enabled toolkit.telemetry.enabled toolkit.telemetry.firstShutdownPing.enabled toolkit.telemetry.newProfilePing.enabled toolkit.telemetry.reportingpolicy.firstRun toolkit.telemetry.shutdownPingSender.enabled toolkit.telemetry.unified toolkit.telemetry.updatePing.enabled browser.newtabpage.activity-stream.feeds.telemetry browser.newtabpage.activity-stream.telemetry experiments.enabled experiments.activeExperiment experiments.supported datareporting.healthreport.uploadEnabled nsITelemetry.canRecordBase nsITelemetry.canRecordExtended devtools.webide.enabled
devtools.onboarding.telemetry.logged = false toolkit.telemetry.updatePing.enabled = false browser.newtabpage.activity-stream.feeds.telemetry = false browser.newtabpage.activity-stream.telemetry = false browser.ping-centre.telemetry = false toolkit.telemetry.bhrPing.enabled = false toolkit.telemetry.enabled = false toolkit.telemetry.firstShutdownPing.enabled = false toolkit.telemetry.hybridContent.enabled = false toolkit.telemetry.newProfilePing.enabled = false toolkit.telemetry.reportingpolicy.firstRun = false toolkit.telemetry.shutdownPingSender.enabled = false toolkit.telemetry.unified = false toolkit.telemetry.updatePing.enabled = false toolkit.telemetry.reportingpolicy.firstRun = false toolkit.telemetry.unified = false toolkit.telemetry.archive.enabled = false devtools.onboarding.telemetry.logged = false toolkit.telemetry.bhrPing.enabled = false datareporting.healthreport.uploadEnabled = false datareporting.policy.dataSubmissionEnabled = false datareporting.sessions.current.clean = true datareporting.healthreport.uploadEnabled = false datareporting.policy.dataSubmissionEnabled = false datareporting.sessions.current.clean = true
So some telemetry has been disabled with a mozconfig. Not sure what all it disables, but it's a start.
Remove Google's telemetry.
Google safebrowsing telemetry:
browser.safebrowsing.allowOverride = false browser.safebrowsing.blockedURIs.enabled = false browser.safebrowsing.downloads.enabled = false browser.safebrowsing.downloads.remote.block_dangerous = false browser.safebrowsing.downloads.remote.block_dangerous_host = false browser.safebrowsing.downloads.remote.block_potentially_unwanted = false browser.safebrowsing.downloads.remote.block_uncommon = false browser.safebrowsing.downloads.remote.enabled = false browser.safebrowsing.malware.enabled = false browser.safebrowsing.phishing.enabled = false services.sync.prefs.sync.browser.safebrowsing.downloads.enabled = false services.sync.prefs.sync.browser.safebrowsing.downloads.remote.block_potentially_unwanted = false services.sync.prefs.sync.browser.safebrowsing.malware.enabled = false services.sync.prefs.sync.browser.safebrowsing.phishing.enabled = false
I knew Firefox is not better than chrome privacy wise. I would also check the TCP connections that the browser does towards the Mozilla servers.
I have been working on setting these to privacy optimized settings by default. Should be included in next release. Will keep open as there is most likely more to do.
According to a user when using r3dfox and Mercury, "it keeps connecting to 93.243.107.34.bc.googleusercontent.com just like R3dfox did. And if I kill the connection it's coming back 5 seconds later."
I assume this is some sort of Google telemetry.
According to a user when using r3dfox and Mercury, "it keeps connecting to 93.243.107.34.bc.googleusercontent.com just like R3dfox did. And if I kill the connection it's coming back 5 seconds later."
I assume this is some sort of Google telemetry.
I'm on r3dfox 122 and I have checked the modem logs, I did not find that url.
boot My r3dfox 124 These mozilla domain names use google cloud
2024/04/10 11:16:04 udp.go:250: detectportal.firefox.com
2024/04/10 11:16:04 tcp.go:1122: SYN 34.107.221.82:80
2024/04/10 11:16:05 tcp.go:1122: SYN 34.107.221.82:80
2024/04/10 11:16:04 udp.go:250: content-signature-2.cdn.mozilla.net
2024/04/10 11:16:05 udp.go:250: firefox.settings.services.mozilla.com
2024/04/10 11:16:05 udp.go:250: push.services.mozilla.com
2024/04/10 11:16:04 tcp.go:1122: SYN 34.107.221.82:80
2024/04/10 11:16:05 tcp.go:1122: SYN 34.160.144.191:443
2024/04/10 11:16:05 tcp.go:1122: SYN 34.107.221.82:80
2024/04/10 11:16:05 tcp.go:1122: SYN 34.107.221.82:80
2024/04/10 11:16:05 udp.go:250: firefox.settings.services.mozilla.com
2024/04/10 11:16:05 udp.go:250: detectportal.firefox.com
2024/04/10 11:16:05 udp.go:250: shavar.services.mozilla.com
2024/04/10 11:16:05 tcp.go:1122: SYN 34.149.100.209:443
2024/04/10 11:16:05 udp.go:250: content-signature-2.cdn.mozilla.net
2024/04/10 11:16:05 udp.go:250: detectportal.firefox.com
2024/04/10 11:16:05 udp.go:250: detectportal.firefox.com
2024/04/10 11:16:05 udp.go:250: prod.content-signature-chains.prod.webservices.mozgcp.net
2024/04/10 11:16:05 udp.go:250: prod.remote-settings.prod.webservices.mozgcp.net
2024/04/10 11:16:05 udp.go:250: autopush.prod.mozaws.net
2024/04/10 11:16:05 udp.go:250: prod.content-signature-chains.prod.webservices.mozgcp.net
2024/04/10 11:16:05 tcp.go:1122: SYN 52.10.78.57:443
2024/04/10 11:16:05 udp.go:250: shavar.prod.mozaws.net
2024/04/10 11:16:05 tcp.go:1122: SYN 34.160.144.191:443
2024/04/10 11:16:05 udp.go:250: prod.content-signature-chains.prod.webservices.mozgcp.net
2024/04/10 11:16:05 udp.go:250: prod.remote-settings.prod.webservices.mozgcp.net
2024/04/10 11:16:05 udp.go:250: autopush.prod.mozaws.net
2024/04/10 11:16:05 tcp.go:1122: SYN 34.149.100.209:443
2024/04/10 11:16:05 tcp.go:1122: SYN 34.107.221.82:80
2024/04/10 11:16:05 tcp.go:1122: SYN 34.107.221.82:80
2024/04/10 11:16:05 udp.go:250: detectportal.firefox.com
2024/04/10 11:16:05 udp.go:250: detectportal.firefox.com
2024/04/10 11:16:05 tcp.go:1122: SYN 34.107.243.93:443
2024/04/10 11:16:05 udp.go:250: prod.content-signature-chains.prod.webservices.mozgcp.net
2024/04/10 11:16:05 udp.go:250: shavar.prod.mozaws.net
2024/04/10 11:16:05 udp.go:250: shavar.services.mozilla.com
2024/04/10 11:16:05 udp.go:250: detectportal.firefox.com
2024/04/10 11:16:05 udp.go:250: shavar.prod.mozaws.net
2024/04/10 11:16:05 udp.go:250: push.services.mozilla.com
2024/04/10 11:16:05 udp.go:250: detectportal.firefox.com
2024/04/10 11:16:06 udp.go:250: shavar.services.mozilla.com
2024/04/10 11:16:06 udp.go:250: push.services.mozilla.com
2024/04/10 11:16:06 tcp.go:1122: SYN 34.149.100.209:443
2024/04/10 11:16:06 tcp.go:1122: SYN 34.107.243.93:443
2024/04/10 11:16:06 tcp.go:1122: SYN 34.149.100.209:443
2024/04/10 11:16:06 udp.go:250: firefox-settings-attachments.cdn.mozilla.net
2024/04/10 11:16:06 udp.go:250: attachments.prod.remote-settings.prod.webservices.mozgcp.net
2024/04/10 11:16:07 udp.go:250: attachments.prod.remote-settings.prod.webservices.mozgcp.net
Question? Do you plan to just disable it or completely remove the telemetry like Basilisk / Palemoon? since they are two completely different things...
I would like to eventually remove it, but if that proves too much for release builds I guess disabling it would be fine too.
This includes Firefox telemetry, Google Safebrowsing, etc.