The third-party program does seem to have library validation disabled: I recommend that you discuss this with the tool’s author. The only good reason to disable library validation is if the tool is loading plug-ins from other third-party developers, which seems unlikely. I see a lot of folks disable library validation because they think it’ll make their life easier but, in reality, it makes things harder. Specifically, the combination of disabling library validation and dangling load commands is the number one cause of mysterious Gatekeeper rejections. See Resolving Trusted Execution Problems for the details. So, unless this tool needs to disable library validation, I recommend that you re-enable it. That’s better for security and it helps with Gatekeeper. I thought about notarising, but as far as I understand you can only notarise Apps or Zip files. Am I missing something? Yes. As a general rule you should not notarise each code item separately. Rather, build all your code items into a complete product
Topic:
Code Signing
SubTopic:
General
Tags: