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.
Both apps have been notarized now, for added security protection, particularly when used in Mojave.
I’m all in favour of better security, so long as it doesn’t make my life any more difficult. Does Notarization fulfil that?
With recent privacy protection, notarization requirements, and extended checking of executable code, it’s getting more common for an app not to launch. What can you do when that happens?