3 ms·
There are a lot of bundle identifier checks in macOS/Mac OS X, including in the system frameworks. Apple could have targeted the AHP bundle id to break things.
by lapcat 4y ago
There are a lot of bundle identifier checks in macOS/Mac OS X, including in the system frameworks. Apple could have targeted the AHP bundle id to break things. Of course, RA could have changed the bundle id or done other hijacking to make it work again, but it would be a cat-and-mouse game that Apple would probably win in the end, because RA customers would continually experience breakage on OS updates.
Also, the "audio hijacker" was located in a well-known system directory, so Apple could just nuke that directory.
That's assuming Apple really wanted to break AHP. It's unclear how much motive Apple had to follow the RIAA request even before the now famous meeting.
- Wowfunhappy 4y agoRight, and Apple also could have introduced Gatekeeper and co six years earlier than they ultimately did, just for their friends at the RIAA! But it all seems pretty far-fetched. I don't think I believe the alternate scenario would have ever happened.
- catiopatio 4y agoWhat about it is far-fetched? Contemporaneously to this story, Apple disabled screen capture of DVD movies and introduced PT_DENY_ATTACH (preventing debugging of the DVD player) at the behest of the MPAA.