# New signature required for each new version of a module?

**URL:** <https://forum.inductiveautomation.com/t/new-signature-required-for-each-new-version-of-a-module/2063>\
**Category:** Module Development\
**Created:** [July 21, 2010, 10:37pm UTC](https://forum.inductiveautomation.com/t/new-signature-required-for-each-new-version-of-a-module/2063 "2010-07-21T22:37:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Automate](https://avatars.discourse-cdn.com/v4/letter/a/51bf81/32.png) [@Automate](https://forum.inductiveautomation.com/u/Automate)\
**Post date:** [July 21, 2010, 10:37pm UTC](https://forum.inductiveautomation.com/t/new-signature-required-for-each-new-version-of-a-module/2063/1 "2010-07-21T22:37:41Z")

</div>

If one goes through the process of getting their module cryptographically signed by IA, do future versions of the same module require a new signature or will the same signature work for new versions of the SDK developed module?

---

<div class="post-metadata">

**Author:** ![Colby.Clegg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby.clegg/32/3282_2.png) [@Colby.Clegg](https://forum.inductiveautomation.com/u/Colby.Clegg)\
**Post date:** [July 21, 2010, 10:50pm UTC](https://forum.inductiveautomation.com/t/new-signature-required-for-each-new-version-of-a-module/2063/2 "2010-07-21T22:50:35Z")

</div>

They’ll need to be signed each time they’re released, but it should be a fully automatic process (most of the time- perhaps initial module release will need some sort of review- we’re going to be figuring out this kind of stuff shortly).

Regards,