I am currently creating an installer for a program using NSIS on a Linux machine. NSIS binaries have been compiled for Ubuntu, and using a .nsi script is straightforward. However, the resulting file setup.exeis unsigned. This leads to scary warnings for our users who download the installer through most common web browsers, as well as warnings from Windows itself at startup.
We would like to avoid these warnings, and if I did not miss something, this requires using the Windows tool to sign the generated setup.exe file. Is there a way to do this on a machine other than Windows?
Unfortunately, each installer is unique (different files included depending on the client’s request and a unique identifier), so I can’t sign the installer on a Windows machine and download it.
source
share