# Updated Ignition/Ignition Designer Launcher receives warning: Unsigned Legacy Designer **URL:** \ **Category:** Ignition\ **Created:** [January 24, 2024, 4:42pm UTC](https://forum.inductiveautomation.com/t/updated-ignition-ignition-designer-launcher-receives-warning-unsigned-legacy-designer/84713 "2024-01-24T16:42:32Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Mausimo](https://avatars.discourse-cdn.com/v4/letter/m/b5a626/32.png) [@Mausimo](https://forum.inductiveautomation.com/u/Mausimo)\ **Post date:** [January 24, 2024, 4:42pm UTC](https://forum.inductiveautomation.com/t/updated-ignition-ignition-designer-launcher-receives-warning-unsigned-legacy-designer/84713/1 "2024-01-24T16:42:32Z")
I updated my Ignition to 8.1.35 and Ignition Designer Launcher to Version 1.1.35. When I "Open Designer" for a Client Gateway address I receive the warning dialog: "Unsigned Legacy Designer The jar for this Designer is from an older version of Ignition and is unsigned. Are you sure you want to launch this designer". I also have debug logging enabled and see this entry: "WARN [SignatureVerifier] [2024/01/24 09:04:57]: Target gateway is too old for launchclient.jar signature verification." I can click okay on the warning and my IgnitionEdge Designer loads as expected, but I am looking to get more info on this warning. My interpretation is that the jar on the Client Gateway is from an older version of Ignition which is incompatible with signature verification using the latest software. Thus, the warning is presented? If I wanted to resolve this warning, would I have to update the Ignition version on the Client Gateways? ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [January 24, 2024, 4:45pm UTC](https://forum.inductiveautomation.com/t/updated-ignition-ignition-designer-launcher-receives-warning-unsigned-legacy-designer/84713/2 "2024-01-24T16:45:24Z")
> [@Mausimo](#): > > If I wanted to resolve this warning, would I have to update the Ignition version on the Client Gateways? Yes, exactly that. The launchclient signature verification is a mechanism we're using to ensure that, from your _local computer's point of view_, the arbitrary file delivered by the remote address that _it's assuming is an Ignition Gateway_, **actually is**. It's a somewhat exotic, but absolutely plausible, attack vector - someone gets onto your network somehow, successfully impersonates a Gateway, and then uses the automatic connection of other computers to retrieve the `launchclient.jar` in order to pivot into local code execution on those other computers. ---
**Author:** ![Mausimo](https://avatars.discourse-cdn.com/v4/letter/m/b5a626/32.png) [@Mausimo](https://forum.inductiveautomation.com/u/Mausimo)\ **Post date:** [January 24, 2024, 4:53pm UTC](https://forum.inductiveautomation.com/t/updated-ignition-ignition-designer-launcher-receives-warning-unsigned-legacy-designer/84713/3 "2024-01-24T16:53:14Z")
Thanks for the information and confirmation!