3 ms·
That behavior goes all the way back to Classic Mac OS. If the above is working as designed, then Zoom automating the copy-app-to-/Applications process doesn't
by xenophonf 7y ago
That behavior goes all the way back to Classic Mac OS. If the above is working as designed, then Zoom automating the copy-app-to-/Applications process doesn't really seem that hinky to me.
- oefrha 7y agoIt’s a weird thing to do, but I don’t find it particularly concerning, no. You launched the installer after all. (I do use Suspicious Package to quicklook pkgs myself, FWIW.)
- xenophonf 7y agoHaving write access without privilege escalation to executable packages run by all users on a multiuser computer is a significant security risk. That's one of the ways an attacker can pivot into other systems from a compromised computer.
- oefrha 7y agoroot:admin 775 is only writable by the admin group, I’m not sure where you got the idea that all users have write access. The situation here is an admin explicitly executing a program that writes to a directory that they have write access to. Edit: corrected typo 755 => 775. Edit 2: Okay, I read what you wrote again and can now see I misunderstood. However, 1. macOS is primarily single user (or at least single household) given how it's actually used. In actual multiuser settings admins don't typically muck around with their admin account. 2. Typically other users can read/execute a lot of stuff that's not root anyway. For instance, on research group Linux servers people would often tell you to just execute something in their home directory.