Currently I generate an installer for a program using NSIS on a Linux machine. The NSIS binaries have been compiled for Ubuntu, and using the .nsi script presents no difficulties. However, the resulting setup.exe file is unsigned. This results in scary warnings for our users who download the installer via most common web browsers, as well as warnings from Windows itself when run.
We’d like to avoid these warnings, and unless I’m missing something, that requires using a Windows tool to sign the generated setup.exe file. Is there a way to do this on a non-Windows machine?
Unfortunately, each installer is unique (different files are bundled depending on the customer’s request, and a unique ID included) so I cannot sign the installer on a Windows machine and then upload it.
I had to do it a few weeks ago, without using wine. What I did was to import the pfx file to windows and then exported it with “Include all certificates in the certificate path if possible” option. then I followed the instruction on this page .
After you have all the certs (spc and pvk files) you should use the following command:
I had to install mono-dev pack: