Whenever an app is opened in 10.14.2, its signature is checked asynchronously, often several times. But in many cases, macOS doesn’t act on any errors returned.
Another worthless piece of “security theatre” about bundle signatures. I wouldn’t bother reading it, or downloading the new version of Signet.
Is checking bundle signatures a waste of time once they have passed their ‘first run’ check? Does macOS ever do that?
Has your Mac got any old apps and other bundles on it? Have their signing certificates been revoked, or are they perhaps unsigned? Here’s a new app to help you find out.
Authentication dialogs to permit access to your keychain are supplied by the macOS security system, and follow a strict pattern.
The workhorses of computer security, message digests and security certificates, are in the process of changing. Some disruption will result.
Another ‘scripting’ exercise in Swift starts with time wasted sorting out signing. But it does get better after that.
How, on the internet, can you prove that you are who you say you are? Could ‘internet IDs’ solve the abuse problem?
Continuing misleading error alerts show that Apple has not fixed problems in the Mac App Store after all.
Most of our financial and personal transactions should be protected by secure Internet connections. A year on, how has the Heartbleed bug changed this?