https://forge.codesys.com/forge/talk/Engineering/thread/56663034e2/2024-04-18T12:23:03.927000ZRecent posts to Codesys installation package fails because not signed2024-04-18T12:23:03.927000Z2024-04-18T12:23:03.927000Zdavecfchttps://forge.codesys.com/u/davecfc/https://forge.codesys.com895003034663aa6bad722dfc793354b6b76f5daf

<div class="markdown_content"><p>Also had this problem when working on legacy project. My packege was CODESYS Code Generator ARM 4.0.3.0.package. To manage this I used PackageManagerCLI.exe. This tool does not validate certificates appearently. My command: "C:\Program Files\CODESYS 3.5.17.30\CODESYS\Common\PackageManagerCLI.exe" --profile="CODESYS V3.5 SP17 Patch 3" --install=""C:\Users\sample_user\AppData\Local\Temp\APInstaller\5wx1k02a.r2t\CODESYS Code Generator ARM 4.0.3.0.package""</p></div>

2022-05-10T18:14:01.092000Z2022-05-10T18:14:01.092000Zrandomplcguyhttps://forge.codesys.com/u/randomplcguy/https://forge.codesys.com8924fe59bbe5949a93f9e804ec1a802a61260e3f

<div class="markdown_content"><p>The procedure you gave was to sign the library, not the package. For future reference you need to use PackageManagerCLI.exe to do so.</p></div>

2022-05-10T13:47:57.867000Z2022-05-10T13:47:57.867000Zrandomplcguyhttps://forge.codesys.com/u/randomplcguy/https://forge.codesys.comf266156d6f2dee89d7c74844225ba27834ca1f61

<div class="markdown_content"><p>Never mind, I found why.</p></div>

2022-05-10T13:47:54.252000Z2022-05-10T13:47:54.252000Zrandomplcguyhttps://forge.codesys.com/u/randomplcguy/https://forge.codesys.com226846f4b14af1ee193e5b4b2dba87313647343a

<div class="markdown_content"><p>Never mind, I found why.</p></div>

2022-05-10T13:39:36.838000Z2022-05-10T13:39:36.838000Zrandomplcguyhttps://forge.codesys.com/u/randomplcguy/https://forge.codesys.comf5776d3808b8eee6ff153f5ca165f6d8bf1aadf2

<div class="markdown_content"><p>Just tried the procedure, and it does not work. I can see it in the certificate store, but for some reason Codesys does not select it in the dialog.</p></div>

2022-05-09T13:36:51.029000Z2022-05-09T13:36:51.029000Zeschwellingerhttps://forge.codesys.com/u/eschwellinger/https://forge.codesys.com6eee14da8e300f005039ca6cfa88853606a53bac

<div class="markdown_content"><p><a href="https://faq.codesys.com/display/CDSFAQ/Code-sign+a+library" rel="nofollow">https://faq.codesys.com/display/CDSFAQ/Code-sign+a+library</a></p></div>

2022-05-09T13:09:07.948000Z2022-05-09T13:09:07.948000Zrandomplcguyhttps://forge.codesys.com/u/randomplcguy/https://forge.codesys.com27778b93e5a3882e1cc3ec9e4d9fb89c51343b95

<div class="markdown_content"><p>I am trying to create an installation package for the Codesys Worbench. While it works fine for Workbench 3.5 SP16 and SP17, it fails for SP17 patch 3 and later. 3S replaced the Package Manager with Codesys Installer. While it supports packages, it fails because my package does not have a signature, even if I clicked on "I want to continue despite of the missing signature(s)".</p> <p>Does anyone know how to sign a package?</p></div>