"Pace sign" is the same as code signing, just done with Pace tool and can be done with a custom certificate. When you re-sign something you are actually removing the previous signature and applying the new one.Fender19 wrote: ↑Thu Jan 16, 2020 6:17 pm I have waded my way through this process and it is working but the "bookkeeping" is really something else. Adding that extra layer of signing (notarization) now requires 3 layers for AAX plugins - code sign + Pace sign + notarize. Get one wrong - or forget a step - or use the wrong password or ID - and the whole thing doesn't work! Many of you clever folk probably have this automated but for now I'm doing it all manually.
Now, something I don't understand is how exactly does all of this prevent malicious software? Hackers are hackers - can't they could just force sign a malicious app and notarize with a bogus account? How is any of this nightmare preventing that?
So you don't need to sign the AAX twice, just do it with the Pace tool.
It's not too difficult to automate all these steps. Check the notarization script posted in this thread (now in OP). If you don't want anything fancy, just copy all your commands in a .sh (for mac) or .bat (for win) and run that instead of re-typing them every time.