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?
TCC
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.
Each now built with the latest version of Xcode, and notarized for your added security. Recommended for Mojave users in particular.
Changes address issues with Kensington and Blizzard software.
How ssh is by default given full access to private data, and how removing it from the Privacy pane only enables that access.
This article is being replaced with a completely fresh one which should be far more accurate.
