# How to start with signing audio plugins?

**URL:** <https://forum.juce.com/t/how-to-start-with-signing-audio-plugins/44972>\
**Category:** Audio Plugins\
**Created:** [March 12, 2021, 8:34pm UTC](https://forum.juce.com/t/how-to-start-with-signing-audio-plugins/44972 "2021-03-12T20:34:55Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![petervorlaender](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/petervorlaender/32/13489_2.png) [@petervorlaender](https://forum.juce.com/u/petervorlaender)\
**Post date:** [March 14, 2021, 12:17am UTC](https://forum.juce.com/t/how-to-start-with-signing-audio-plugins/44972/16 "2021-03-14T00:17:46Z")

</div>

Ah, interesting. I also observed this when I accidentally forgot to enable the hardening.

But my understanding is: when the host running the plugin has the hardened runtime enabled, then also the plugins need to have the correct entitlements; otherwise that would put a big hole  
into the whole security philosophy of “hardened runtime”, no?

At least [here](https://forum.juce.com/t/unable-to-host-vst3-plugins-on-macos-the-bundle-is-damaged-or-missing-necessary-resources/36939/3) @op414 seems to have experienced this. I am not sure if there are hosts out in the market where you currently run into this problem, but i thought its better to err on the safe side.

---

_[View the full topic](https://forum.juce.com/t/how-to-start-with-signing-audio-plugins/44972)._