Apple has pushed an update to the data used by TCC, the privacy protection system in macOS 10.14 […]
TCC
Checks the entitlements and settings of apps for accessing private data in Mojave, with a custom log browser to help diagnose problems.
Look in Activity Monitor or the log, and you won’t find anything named Gatekeeper, is its a team of different systems, each of which can work on its own. Here’s the detail and a diagram.
With apps in future set to come from the App Store or notarized by Apple, entitlements are going to be the rule not an exception.
Mojave’s privacy features remain essentially undocumented. Apple hasn’t explained how command tools negotiate TCC’s protection. Why not, and what should we do?
Apple has intentionally made it very hard to troubleshoot problems with privacy protection. Here’s a new feature to help, in a new version of Taccy.
One important requirement for code signatures is with Mojave’s new privacy controls. Are they needed, though?
The differences between a full Gatekeeper check, an AMFI check for integrity, and a normal app open, and why signature errors can be tolerated.
Updated late last week, Apple has provided no information about this. What’s more, installing the update may be insufficient to apply it.
What may be a robust strategy for security in macOS 10.15 might leave many users of older versions stranded. This needs discussion.
The Eclectic Light Company 