Oh well - time to go clean up my Windows installs. sigh
---
I used to keep one last Windows 7 box around. It had the default firewall policies set to block everything by default and I had even went so far as to disable all the default rules that Windows creates and added explicit rules to only allow the specific traffic to the specific internal services I actually needed.
Then, I installed Firefox one day so I could use it to access a few internal web sites. Shortly afterwards, I went to add new firewall rules to allow connections to these internal web sites and discovered that the installer had automatically added new firewall rules for Firefox allowing it to connect to anything anywhere! Fortunately, this host was on a subnet which was blocked in the "real" firewall anyways, so -- in this case -- no actual harm done (it couldn't get out to the Internet anyways) but I was still a bit surprised to discover that.
Can you imagine the fallout and calls for beheading that would occur if Firefox for Linux added new rules to your Linux hosts' iptables firewalls!?
Or has Mozilla adopted a dark pattern where all the privacy-violating checkboxes are automatically "chosen" by default?
Hell, if you have a "clean" host/VM, I encourage you to install Firefox, start a packet capture, launch Firefox for the first time, then just sit and wait for 30 seconds or so -- not doing anything or interacting with it in any way -- before closing Firefox. Then, go take a look at your packet capture. I think you'll be quite surprised at all of the connections it makes...
This is really not the Mozilla Firefox I envisioned or expected way back when I first started supporting and advocating for it (when it was first announced!).
This is worrisome. Is there a modern browser available that doesn’t try to spy on you?
New-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Mozilla\Firefox" -Name DisableDefaultBrowserAgent -PropertyType DWord -Value 1
To disable the scheduled task (if you simply delete it, it might "reappear" after Firefox is updated): schtasks.exe /change /disable /tn "\Mozilla\Firefox Default Browser Agent 308046B0AF4A39CB"
Or, you could simply disable the telemetry altogether and tell Mozilla that all this "opt-in by default" telemetry is bullshit.Note: The above are untested as I don't run Windows (partly because of all the spyware -- excuse me, "telemetry" -- bullshit!).
(Edit: Sorry, changed forward slashes to back slashes.)
BTW, your suggestions do not in the firefox I have:
New-ItemProperty : Cannot find path 'HKLM:\SOFTWARE\Policies\Mozilla\Firefox' because it does not exist. At line:1 char:3 + New-ItemProperty -Path "HKLM:/SOFTWARE/Policies/Mozilla/Firefox" -N ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (HKLM:\SOFTWARE\Policies\Mozilla\Firefox:String) [New-ItemProperty], ItemNotFoundException + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.NewItemPropertyCommand
ERROR: The specified task name "\Mozilla\Firefox Default Browser Agent 308046B0AF4A39CB" does not exist in the system.
New-Item -Path "HKLM:\SOFTWARE\Policies\Mozilla\Firefox"
might be neccesary first, if Firefox didn't already create it. Or it could be because I originally used forward slashes instead of back slashes (now fixed!).