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.
signature
Just fill in this form – then the problems start. They look fine in Preview or another app, but don’t work right. Here’s why.
Preparing software for distribution shouldn’t be harder than writing the code in the first place.
Confused as to what will and won’t run on macOS 10.15 Catalina? Here’s a clear guide for users from regular to advanced.
It took 5 apps, 4 command tools in 6 commands, 2 developer certificates and an app-specific password for 260 lines of code.
Important changes for anyone distributing command tools in particular, and a good time to ensure you only ship signed and notarized apps if possible.
Crawls selected folders checking all app signatures. Reports all signatures which have problems, including unsigned apps.
App signatures are only checked on app first run – it may once have been true, but is no longer accurate. But can you bypass those additional checks? Is this a vulnerability?
How can an app check that nothing has nobbled it? How to use its code signature to perform a simple launch test.
Do you use digital signatures in PDF documents, or do you trust your PDF reader to check them? You could be spoofed into trusting forgeries.
