<!DOCTYPE html>
<html data-lt-installed="true">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body style="padding-bottom: 1px;">
<blockquote type="cite"
cite="mid:mm6ebj9t6juq45stqjk8hel960hr6nm83c@4ax.com">
<pre wrap="" class="moz-quote-pre">And now I am getting a request for "signing" the applications (and/or possibly
the installers made by InnoSetup) and I have no idea on how to do this.</pre>
</blockquote>
<p>Signing an FPC application can be done completely independent of
FPC/Lazarus applying singntool (from Windows SDK) to compiled
binary.<br>
</p>
<p>InnoSetup has support for singing, it also can sign uninstaller
executable.<br>
</p>
<blockquote type="cite"
cite="mid:mm6ebj9t6juq45stqjk8hel960hr6nm83c@4ax.com">
<pre wrap="" class="moz-quote-pre">Apparently some customers cannot install the software because of IT department
policies prohibiting running unsigned programs...</pre>
</blockquote>
<p>In addition they have to trust your certificate used for signing.</p>
<p>Technically you can sign using an selfsigned certificate. But
"IT-Department" has to add that to trustlist.</p>
<p>Presumably you have to by an codesign certificate<br>
</p>
<p><br>
</p>
<blockquote type="cite"
cite="mid:mm6ebj9t6juq45stqjk8hel960hr6nm83c@4ax.com">
<pre wrap="" class="moz-quote-pre">What to do about this? Most involved products are for Windows and they are 32
bit.</pre>
</blockquote>
<p>There is no difference in signing 32 or 64 Bit.<br>
</p>
<blockquote type="cite"
cite="mid:mm6ebj9t6juq45stqjk8hel960hr6nm83c@4ax.com">
<pre wrap="" class="moz-quote-pre">The process should be possible to be applied to already existing exe files
because the builds can no longer be performed since the original dev
environments no longer exist.</pre>
</blockquote>
<p>You should exclude FreePascal / Delphi from your search - just
look for signing win32 application.</p>
<p>Elmar</p>
<p><br>
</p>
</body>
<lt-container></lt-container>
</html>