How deeply does macOS check a signature? What are all the static code validation flags? Should my app leave macOS to perform signature checks?
How checks differ when an app is launched from a new path, and the effects of gross changes to the Resources folder, and small changes to code.
Why signature checks are so complex, and a walk through log entries of a notarized app launching normally in macOS 10.14.5.
With a shiny new high-speed Samsung X5 SSD to test, I was looking forward to some real speed. Did it deliver good value for its high price, though?
Now can check apps (bundles with the extension .app) to determine whether they’re notarized, from Apple, App Store, etc.
How long should it take for Apple’s Notary Service to notarize an app of yours? Analysis of over 100 runs over 8 months.
Signature checks are complex. On first run with a quarantine flag, they include the contents of the Resources folder, but seldom do after that.
SwiftUI, notarization, malware detection, and Time Machine for APFS: all look worryingly incomplete in Catalina. Are they a bit premature?
You don’t have to add an Info.plist to a standalone Mach-O tool in order to sign it, or to get it notarized successfully. And more tips.
System Integrity Protection can get in your way, and may be recommended to solve compatibility problems. It’s also changing again in Catalina.