Hi everyone,
I’ve recently finished developing my plugin, and I’m now looking to get started with code signing. I’m a bit unsure of where to begin with the process, so I’d really appreciate any advice or recommendations you could share.
I know I need an Apple Developer ID for macOS, but what’s the best approach for Windows? I’m not ready to commit to paying $500 to a company like DigiCert, so I was wondering if there are any more affordable options or if code signing might not even be necessary. I’m also curious about the process for code signing AAX plugins for Pro Tools.
Any insights or suggestions would be super helpful. Thanks in advance!
ibisum
November 7, 2024, 10:34am
2
If you haven’t seen @sudara ’s excellent treaty on the subject, get yourself a warm cuppa and digest this asap:
macOS code signing is something plugin devs tend to put off or avoid. It's fairly straightforward, but there's some details to pay attention to.
Est. reading time: 9 minutes
See also this thread, detailing another JUCE’ers adventures with the subject:
For the bonus round, read the Github Action code which @sudara has prepared for us in his pamplejuce template project:
A JUCE audio plugin template. JUCE 8, Catch2, Pluginval, macOS notarization, Azure Trusted Signing, Github Actions
Specifically, line 153:
(Read the rest too:)
https://github.com/sudara/pamplejuce/blob/main/.github/workflows/build_and_test.yml
2 Likes
Qfactor
November 7, 2024, 11:42am
3
Hi all,
I’m sure many of you are aware of the increasingly tight restrictions on code signing in the last few years on Windows.
We’ve seen a bunch of different ways of doing code signing, from key files (no longer supported) to HSMs/dongles to remote HSMs such as Azure Key Vault, but the most recent addition comes in the form of a new Microsoft Azure service called Azure Code Signing which is super easy to use once you get it set up.
In a sense, it is very similar to how Let’s Encrypt works i…
all the way (it’s 10.76€ per month)
And it also works for AAX plugins. KoalaDocs/azure-code-signing-for-plugin-developers.md at master · koaladsp/KoalaDocs · GitHub also includes info about that in section 2.3.4.
Or if you don’t want to read and want to subcontract this, feel free to PM and I’ll get your scripts ready
1 Like
zsliu98
November 7, 2024, 12:15pm
4
In case you have not contacted Avid:
- __Android__: Android 5 - Lollipop (API Level 21)
## Contributing
Please see our [contribution guidelines](.github/contributing.md).
## Licensing
See [LICENSE.md](LICENSE.md) for licensing and dependency information.
## AAX Plug-Ins
AAX plug-ins need to be digitally signed using PACE Anti-Piracy's signing tools
before they will run in commercially available versions of Pro Tools. These
tools are provided free of charge by Avid. Before obtaining the signing tools,
you will need to use a special build of Pro Tools, called Pro Tools Developer,
to test your unsigned plug-ins. The steps to obtain Pro Tools Developer are:
1. Sign up as an AAX Developer [here](https://developer.avid.com/aax/).
2. Request a Pro Tools Developer Bundle activation code by sending an email to
[devauth@avid.com](mailto:devauth@avid.com).
