Sign Windows installer/binaries using Authenticode about onionshare HOT 5 CLOSED

Thanks for posting this, I just marked it for the 0.4 milestone.

from onionshare.

I'm finally getting around to jumping through the hoops. I need to wait 3 days for certum to respond to me. Hopefully the 0.6 release (which is basically done right now) will be signed with Authenticode, but if it ends up taking too long I might push it back to the 0.7 release.

More information about the Authenticode code signing process, for reference:
http://www.tech-pro.net/code-signing-for-developers.html
https://knowledge.verisign.com/support/code-signing-support/index?page=content&id=AR190
http://msdn.microsoft.com/en-us/library/aa387764.aspx
http://msdn.microsoft.com/en-us/library/aa388170.aspx

Here's a page on including codesigning in the build process:
http://nsis.sourceforge.net/Run_Command_After_Compilation
(though I think it will be easier to just add the signtool.exe commands to build_exe.bat)

from onionshare.

I'm waiting on Certum for a free code signing cert, but I'm actually considering ignoring that one and using StartSSL instead. I already have class 2 verification with them, I'm using them for SSL for onionshare.org, so it also won't cost anything extra. And I found a nice tutorial: http://blog.assarbad.net/20110513/startssl-code-signing-certificate/

from onionshare.

Re-opening this because right now it's only signing onionshare.exe and the installer OnionShare_Setup.exe, but not uninstall.exe. When users try uninstalling onionshare they get a scary warning.

from onionshare.

This will be helpful in signing the uninstaller: http://nsis.sourceforge.net/Signing_an_Uninstaller
But it also looks super hacky. Hopefully it won't be too bad.

from onionshare.