Code Signing Identification

[resonant]

When you sign to Apple Developer Program (which costs $99 yearly),

• You will be given a Team ID, this is your Developer ID. You can see it from here: https://developer.apple.com/account/#/membership/

• If you need signing ID for signing your plugins from outside of Xcode, just use your certificates' full numeric name, for example;
  "Developer ID Application: YOUR NAME (YOUR TEAM ID)" You can see it from Keychain Access tool on Mac ;) :)

[d.healey]

What happens after your subscription expires? Can you no longer sign new plugins? What happens if you don't sign them?

[orange]

@d-healey I needed this certificate in order to sign AAX plugins. For Mac AU / VST you don't need to sign.

When the certificate date expires, you need a new certificate for new plugins. (Old signed plugins won't be affected, because they have been already signed)

However I think you can create a self signed certificate and sign the AAX plugins with it. I haven't try that yet, I use Apple developer certificate but one of my friend says that he don't use Apple Developer certificate for AAX.

[Dan Korneff]

@orange said in Code Signing Identification:

However I think you can create a self signed certificate and sign the AAX plugins with it. I haven't try that yet, I use Apple developer certificate but one of my friend says that he don't use Apple Developer certificate for AAX.

I went with self-signing for AAX. No problems on this end so far

[d.healey]

That's good to know. How do you self sign? What about signing installers, is that necessary?

[orange]

@dustbro said in Code Signing Identification:

@orange said in Code Signing Identification:

However I think you can create a self signed certificate and sign the AAX plugins with it. I haven't try that yet, I use Apple developer certificate but one of my friend says that he don't use Apple Developer certificate for AAX.

I went with self-signing for AAX. No problems on this end so far

Cool. So did you use "Keychain Access" to create certificate? And no problem on other computers while opening the AAX plugin?

[Dan Korneff]

@orange I created a .p12 certificate on my PC and then imported into keychain.
Eden tools recommends you use a authorized digital signing service, but I haven't had any issue with beta testers on multiple rigs yet.

[orange]

@dustbro Cool. For PC, I created p12 certificate on MAC and transferred into PC :) The reverse process :) but I see that it works both ways...
I will use self signed p12 certificate on MAC and PC both ;)

I think the Apple Developer certificate is useful for iOS applications, but no need for signing of AAX plugins.

[d.healey]

How does you create a certificate?

[Lindon]

@d-healey perhaps like this?

https://www.sslsupportdesk.com/export-ssl-certificate-private-key-pfx-using-mmc-windows/