Apple’s recent change in requirements for notarization also affects privacy protection in both Mojave and Catalina.
Coming in just a few weeks now, if you’re going to upgrade early to Catalina, now’s the time to start preparing with these tips.
How can you tell whether a notarized app has been hardened, which Apple claims makes it more secure?
Many small independent developers have put a lot of effort into getting their app notarized. Then Apple changes the rules. What does this mean for users, and our security?
App compatibility with Catalina is different: although some may be slightly incompatible, many apps simply don’t run at all. How can you tell which are OK?
Newly-built apps supplied by developers outside the App Store need now to be notarized. This in turn requires hardening, but what is that?
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?