Reply to Thread

Re: code signing

You are welcome

Friedrich

Re: code signing

Got it....thanks!

Re: code signing

Yes, that is correct. When you have General Information -> Digital Signature -> Add a Digital Signature -> set to YES then the compiler will automatically code-sign your generated setup.exe. Compiler report should look similar to the attached screenshot.

Friedrich

Re: code signing

In the script it looks like I'm signing my application .exe but I don't see where setup.exe is being code signed.

#code-sign application "C:\Installation Programs\Release\DataBinder.exe"


I went to General Information and added digital signature to installer executable.

Re: code signing

Microsoft recommends that commercial software publishers code sign all their PE files. And if you would like to see your own application files flagged as 'suspicious' by anti-virus and anti-spyware systems on a regular basis, then don't code-sign ;-)

You should always code-sign your own PE application files (all your .exe, .dll, .ocx, ...). You should not code-sign 3rd-party files because code-signing means that you take over responsibility (and sometimes it is not even allowed to code-sign because the signature modifies the binary contants of a file). If you have "unsigned" 3rd-party components, you should ask the vendor to code-sign the files.

Friedrich

Re: code signing

I meant the setup.exe. Is there any reason I'd want to also the digital signature to my application.exe file?

Re: code signing

With "my app", do you mean the "setup.exe" or your application file(s)?

General Information -> Digital Signature -> Add a Digital Signature -> YES will always code-sign your install. The #code-sign application directive lets you add an Authenticode® digital signature to your own application file(s). For example, your own .exe, .dll, .ocx, etc.

Friedrich

Re: code signing

Got it...thanks.....it worked fine once I got all the pieces in place.

I assume every time I compile an updated version of my setup, my app will be "code-signed" during compilation

Re: code signing

The .PFX is all that you need! SetupBuilder can use both .PVK/.SPC and .PFX.

1. You need SIGNTOOL.EXE from Microsoft.

2. Open the IDE and select "Tools" -> "Options..." -> File Locations tab. In the "Signcode.exe or SignTool.exe Location" field, please specify the fully qualified path to SIGNTOOL.EXE file.

Now open your project and go to "General Information" -> "Digital Signature" -> and select your certificate file (.pfx) in the "PFX File (optional)" field. Enter all required information (including timestamp).

Compile and you are done

Friedrich

Re: code signing

I used firefox to download....I guess that was a mistake. I followed the instructions on copying it but I ended up with a .pfx file and no .spc file. What do I do know.