Discovering what has been updated in a macOS update isn’t easy. In the case of command tools, it’s just impossible.
How apps can opt to set the quarantine flag on files they create, and how macOS can override that to protect you.
Five different classes of metadata, from file system attributes to embedded Info.plist files, explained and explored.
Do you want to see exactly what protected resources an app can try to access? Or check that your own app is correctly configured?
Version numbers are simple, aren’t they? So how come so few of Apple’s own apps conform to its own rules? And as for copyright info, forget it, as so many Apple apps seem to.
Adding support for Mojave’s new privacy system is mandatory for apps which need to access protected data. How easy is that?
Four versions of the same app to demonstrate different app states in Sierra and High Sierra, and how your apps can join the undead.
This week, I have been attacked by zombies – half-dead apps which appear to have quit automatically, but […]
Why would anyone tell the user that an app had quit, but actually leave it hanging around, near-useless, in memory?