3 ms·
> I feel like it's slightly dishonest not to mention that (according to the Chrome devs) this problem is caused by poorly-behaved modifications to the Chrome in
by aikah 10y ago
> I feel like it's slightly dishonest not to mention that (according to the Chrome devs) this problem is caused by poorly-behaved modifications to the Chrome installer made by third-party redistributors, and not by Chrome itself.
What do you mean ? if I download Chrome from the official website I get a third party installer ? because I have the exact same problem with that very official installer.
- DannyBee 10y agoHe means that bug report is about a third party installer screwing up the permissions and nothing changing it? Can you point me to an official installer with the same problem? I'm not aware of those installers installing anything as root.
- rhizome 10y agoOddly the author leaves out any mention of possibilities along these lines.
- dunham 10y agoIt looks like the linked article has been updated at the end to clarify. It sounds like some third party extension's installer (e.g. DivX) is reaching into Chrome.app and mucking with permissions (setting owner to root). Not sure why they don't install into "/Library/Internet Plug-Ins" (maybe it doesn't work with chrome anymore?) (Edit: but a comment in the linked bug report suggests that this may also occur if Chrome is installed as one user and used by another.)
- ameliaquining 10y agoThe bug report claims that in the different-user case you do get a privilege escalation prompt.