Good to know about this privacy issue.
However, if we need fix this issue only on one, maybe two computers, I would prefer to do it manually with the steps described in the linked website:
about:config dom.private-attribution.submission.enabled set to false
In the environment with lot of computers, I would prefer to download the script to one computer, check if it is not malicious and then run the desired command on the other computers - especially if the script is similar one-liner as this one :-)
you can see what the script runs at the top of the page
echo 'user_pref("dom.private-attribution.submission.enabled", false);' | tee -a $HOME/.mozilla/firefox/$(grep "Default=.*\.default*" "$HOME/.mozilla/firefox/profiles.ini" | cut -d"=" -f2)/user.js echo 'Restart Firefox for the change to have effect'
reply
I know, this is what the script does. It is safe now, but what about tomorrow, or next week, month, year? It can be changed, the domain registration could expire (after one year) and then it could be registered by someone with the malicious intents. This is why I prefer to examine the random script downloaded from the Internet before executing it in the production :-)
reply