<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to Signing Packages without exposing the password of the certificate</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/54ae6b4c4a/" rel="alternate"/><link href="https://forge.codesys.com/forge/talk/Engineering/thread/54ae6b4c4a/feed.atom" rel="self"/><id>https://forge.codesys.com/forge/talk/Engineering/thread/54ae6b4c4a/</id><updated>2024-08-20T11:00:16.879000Z</updated><subtitle>Recent posts to Signing Packages without exposing the password of the certificate</subtitle><entry><title>Signing Packages without exposing the password of the certificate</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/54ae6b4c4a/?limit=25#9ec9" rel="alternate"/><published>2024-08-20T11:00:16.879000Z</published><updated>2024-08-20T11:00:16.879000Z</updated><author><name>kevinrn</name><uri>https://forge.codesys.com/u/kevinrn/</uri></author><id>https://forge.codesys.com36f69db534fd801f73de7e6b01908fee72150b52</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Indeed, I'm also seeking a solution for this issue. The main challenge we face is the requirement to use EV (Extended Validation) Certificates. Due to security considerations, it's not possible—nor is it ever recommended in such cases—to export the certificate with its private key.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Signing Packages without exposing the password of the certificate</title><link href="https://forge.codesys.com/forge/talk/Engineering/thread/54ae6b4c4a/?limit=25#b731" rel="alternate"/><published>2023-03-31T08:13:44.208000Z</published><updated>2023-03-31T08:13:44.208000Z</updated><author><name>mauro</name><uri>https://forge.codesys.com/u/mauro/</uri></author><id>https://forge.codesys.com56d54956f99581f5da7f49d75bbfa7e09fe714d5</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Using Microsoft signtool.exe I can install the certificate inside my PC and then use the certificate to sign the file without providing the password. Is there a flag to do the same using PackageManagerCLI.exe? &lt;/p&gt;
&lt;p&gt;This would be a very welcome feature as otherwise I would be forced to leave the certificate password inside a batch file which does not seem to me to be acceptable from the security point of view.&lt;/p&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="err"&gt;Microsoft sign tool:&lt;/span&gt;
&lt;span class="err"&gt;signtool.exe sign /td SHA256 /fd SHA256 /f myCertificateFile.pfx /p myCertificatePassword /tr ...&lt;/span&gt;
&lt;span class="err"&gt;signtool.exe sign /td SHA256 /fd SHA256 /n "My Certificate Name"                          /tr ...&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;


&lt;div class="codehilite"&gt;&lt;pre&gt;&lt;span&gt;&lt;/span&gt;&lt;span class="err"&gt;CODESYS/3S sign too:&lt;/span&gt;
&lt;span class="err"&gt;PackageManagerCLI.exe --pkcs12Path="myCertificateFile.pfx" --pkcs12Passwd="myCertificatePassword" --tsaTimestampServiceUrl= ...&lt;/span&gt;
&lt;span class="err"&gt;PackageManagerCLI.exe --pkcs12????="My Certificate Name"                                          --tsaTimestampServiceUrl= ...&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;


&lt;p&gt;Thanks in advance for your suggestions&lt;br/&gt;
Mauro&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>