> Unfortunately, it is a client-side issue affecting both 11.0.1 and 11.1 clients. So there’s not much Apple can do to provide a fix.
Seems rather unlikely to be true.
Seems rather unlikely to be true.
This would make sense, if you set up remote code execution for apple servers, but I could not imagine something horrible like that.
The server is the the apple server the update process talks to to figure out what to download (and then to download it).
(I haven’t looked at it but there are probably multiple mac processes, with their own set of relationships, and multiple Apple services involved, but for the purpose of this issue, you can think of the client side being anything running on your mac, and server side as anything running on an Apple server.)