sign for macOSAnswered
I created .pkg file and sign with Developer ID installer and then do Notarization.
But Apple refuse to do notarization on that pkg file .
In the LogFileURL they mentioned errors and for systa and libTurboActivate.dylib : "The binary is not signed."; "The signature does not include a secure timestamp."; "The executable does not have the hardened runtime enabled."; "The binary is not signed with a valid Developer ID certificate."
Ok then I tried before I created .pkg to do sign on systa with "Developer ID Application" using:
codesign -s "Developer ID Application: …" /path to/systa
but I am getting error: internal error in Code Signing subsystem
Do you maybe know what is about, what is issue here?
The next version will be signed. We used to sign for macOS (Mac OS X), but then Apple rug-pulled the EV signing that was dominant on Windows & Mac OS X so they could develop their own-controlled signing mechanisms.
More monopolistic tendencies anti-trust regulators should poke Apple for.
This new anti-competitive/monopolistic mechanism also required a bunch of extra steps and complications.
Long story short: you can sign them in the meantime.
The next released version will be signed by us (we’ve bowed to Apple’s anti-competitive behavior because we have no other choice than to do it — Paging the FTC & E.U. Regulators).