Privacy protection differs between GUI and the command line, causing anomalies which are being exploited to steal private data.
How to gain access to protected folders without having to add anything to the Privacy pane yourself. Now being exploited in the wild.
Now runs native on both Intel and Apple Silicon Macs, from Sierra to Big Sur beta 4.
Both apps now detect and report apps which have been built using the 11.0 SDK, and ArchiChect reports non-Intel architectures too.
What is the Accessibility list for in the Privacy tab of Security & Privacy? If you don’t use any Accessibility features, does it do anything?
Where does Apple warn the user that four stray files in an unprotected folder are specially protected by the Sandbox kernel extension?
Additional to the protected folders listed in the Privacy pane, macOS has a secret list of files which are also read-only. Apple hasn’t documented these.
Unique because Location Services isn’t managed by TCC, but by its own locationd service, and is invariably shared in iCloud.
Running an AppleScript which tries to run a shell command with root privileges can fail. Here’s why, and what we can’t do about it.
Despite the lack of documentation from Apple, here’s a full rundown on the only tool provided to control privacy settings.