- Last Active
I can’t stop myself, I have to contribute my opinion.
Keystone is the real villain here. Google’s auto-update mechanism that has root privileges and can change any file anywhere on my system at any time without my permission. Sure, what could go wrong with that!??
Back in 2017 I warned colleagues about the risk of it going wrong and linked to a page of Keystone clear-out instructions. See if you’re infected and what it’s been up to with:
$ defaults read com.google.Keystone.AgentThere are standalone/non-auto-updating versions available if you really need Chrome for testing/compatibility purposes.
Their actual client software installation process also subverts the normal MacOS expected process. The unusual approach fails to provide the user the opportunity to review the product and installation files prior to installation. Specifically, they use the “This package will run a program to determine if the software can be installed.” step to actually perform the actual installation and to write configuration files outside of the program causing MacOS to run the software at each subsequent Startup!
I have been in contact with the developer on this topic and they eventually provided a different installer that behaved as a normal installation. However they declined to make this the default download from their site. So my advice; avoid Zoom.