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?
How long should it take for Apple’s Notary Service to notarize an app of yours? Analysis of over 100 runs over 8 months.
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.
Preparing software for distribution shouldn’t be harder than writing the code in the first place.
The two biggest changes in Catalina are loss of 32-bit software and the requirement for notarization – which also affects Mojave. All is explained.
Apple provides detailed information about how to stunt your Mac’s performance to mitigate against MDS, but doesn’t mention how notarization has become mandatory, and can block extensions and apps from running.
Is notarization just ‘security theatre’? How easy would it be to distribute malware through a legitimate distributor outside the App Store?
Apple’s latest information on notarization can appear alarming and contradictory. Do you need to notarize your own apps and scripts? More helpful guidance.
Apple has just warned developers that rules on notarization will change in macOS 10.14.5. Will users be affected?
What may be a robust strategy for security in macOS 10.15 might leave many users of older versions stranded. This needs discussion.