# Designer startup : Verifying Signature of Designer

**URL:** <https://forum.inductiveautomation.com/t/designer-startup-verifying-signature-of-designer/82670>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [December 4, 2023, 4:27pm UTC](https://forum.inductiveautomation.com/t/designer-startup-verifying-signature-of-designer/82670 "2023-12-04T16:27:35Z")\
**Posts on this page:** 1\
**Showing post:** 32

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [August 17, 2024, 11:44am UTC](https://forum.inductiveautomation.com/t/designer-startup-verifying-signature-of-designer/82670/32 "2024-08-17T11:44:08Z")

</div>

Same answer as I supplied over here:

> [@How to turn off certification revocation check in Ignition 8.1.37?](https://forum.inductiveautomation.com/t/how-to-turn-off-certification-revocation-check-in-ignition-8-1-37/86440/14):
>
> So, you want the target that the launcher is trying to verify to supply the verification criteria? Like a fox in the henhouse? To be secure in today's environments, certificates are supposed to be verified. Any setting to reduce that security has to be deliberate, and not involve the target to be verified.

---

_[View the full topic](https://forum.inductiveautomation.com/t/designer-startup-verifying-signature-of-designer/82670)._