3 ms·
> As a user, I want my OS vendor to have this power and use it appropriately. As a user I want my OS vendor to have this power with my explicit permission and
by AlexandrB 6y ago
> As a user, I want my OS vendor to have this power and use it appropriately.
As a user I want my OS vendor to have this power with my explicit permission and use it appropriately. I also want to be able to disable this completely if I choose.
There's going to come a time where Apple is going to do something shitty with this ability. Giving up the freedom to run whatever code you want on your computer is dangerous long-term.
- veidr 6y agoYep, I do share your concern. They so far haven't done anything shitty with this capability (unlike the one the main thread pertains to, which they have done over and over). There absolutely should be a mechanism to disable the feature, although I think it should be enabled by default.
- ben509 6y ago> There's going to come a time where Apple is going to do something shitty with this ability. Or even "someone who has the credentials Apple owns" does it. I presume they require more than one employee to be able to do that, but that only mitigates insider threat, it doesn't remove it. They could also potentially be fooled into doing some damage. Trust should never be evaluated on whether you think people are trustworthy; bad actors can impersonate, coerce or confuse good actors.
- vaxman 6y agoThe idiot you are replying to has no clue how apps work on the Mac --remotely killing a bundle identifier is not sufficient to stop a piece of malware. to cleanup a mess, they at least have to run a script that makes all kinds of changes, including to launchd, etc. to me that is a remote login --but someone using the F word can argue semantics and get me downvoted and flagged and whatever (as if I give a damn lol --I have 40 years of experience and 30 of it is programming Macs)