Mac OS PList: what additional entries do I need above the standard ones ? (this is the only one I am adding so far)

MacOSX and iOS
1

I’m building my first plugin on the Mac, AU, VST3 and AAX.

My Plist has about 20 entries - standard ones you’d expect from a JUCE project - and I manually added one more to a build of one of my formats:

<key>com.apple.security.cs.disable-library-validation</key><true/>

Are there any more you add personally?
I toyed with the idea of adding:
<key>com.apple.security.cs.allow-unsigned-executable-memory</key><true/> but I think this has to do with JIT, and I don’t think it applies to me.

My plugin is just a simple distortion type of plugin.

2

I think you would only need that 1st one (disable-library-validation) if your plugin is itself loading other plugins or dynamic libraries.

1 Like
3

My plugin is not hosting other plugins. Its essentially a type of simple distortion plugin.
There are others I’m looking into, such as these.

com.apple.security.cs.disable-executable-page-protection
com.apple.security.cs.allow-unsigned-executable-memory
com.apple.security.files.user-selected.read-write
com.apple.security.cs.allow-dyld-environment-variables
4

In general, you should not need to add entitlements to your generic effects plug-in, unless you are doing something special like hosting another dynamic library (such as a plug-in).

Many of the runtime exceptions you have listed are only applicable if you have enabled “hardened runtime”, which you might need to do if you were making an app. The exceptions would loosen the restrictions of the hardened runtime.

Learn more about entitlements here:

One area that you could look into would be making your plug-in “Sandbox safe” for GarageBand.

5

Adding entitlements just for fun doesn’t make much sense. You should only add those you actually need for some feature. If your plugin works, why would you want to add further entitlements? You’ll notice that some entitlement is missing when a feature you build doesn’t work because of it.

6

For one of the plugin formats mention in my OP, there is specific mention of those entitlements in the documentation. I’ve not added those I mentioned, except com.apple.security.cs.disable-library-validation which I am now reviewing.
I don’t want to add entitlements for fun because I’m aware that perhaps the plugin could be open to security risks.
I’m not very experienced in this area of Mac OS distribution, which is why I appreciate you guys inputting.

7

We didn’t add any extra entitlements for our plugins. We leave that stuff alone.

1 Like