Tito SwinefluHoly shit. I only use chrome when I have to for work, and these assholes...
https://www.thatprivacyguy.com/blog/chrome-silent-nano-install/
Iris Young (he/they/she) (PhD)@tito_swineflu ughhh have you figured out a way to get rid of it without it automatically coming back?
Mx. Luna Corbden 🐸@iris @tito_swineflu I'll have to check if my Vivaldi is affected.
If I had this issue, I'd try creating an empty weights.bin file and then locking down the permissions.
ferricoxide@corbden @iris @tito_swineflu
For UNIX/Linux environments, something like:
1. Stop Chrome
2. Execute:
sudo -i
SUDO_HOME="$( eval echo "~${SUDO_USER}" )"
for TARG in $( find ${SUDO_HOME} -name weights.bin 2> /dev/null ); do
rm "${TARG}"
install -bDm 0600 -o root -g root /dev/null "${TARG}"
done
Ought to work?Notes:
* If you use multiple profiles and suspect you might have more than one such file, that should take care of them all
* Depending on your
sudo version, explicitly setting SUDO_HOME might be unnecessary@ferricoxide @corbden @iris i just piped /dev/null into the file. It wasn't rewritten upon restarting chrome.
@tito_swineflu @corbden @iris Other threads have indicated that nuking or corrupting the file results in re-creation. I was trying to prevent re-creation. :)
@ferricoxide @corbden @iris i think that's for deleting it. I don't think chrome validates the file beyond its existence