Electron-builder: Signtool on programmatic usage(question)

[daffylumampao]

Hi,

I have a question. How can you assign this type of signtool programmatically? Can you give me an elaborate example? I am currently using 'NSIS' for windows.

SignTool=signname"{#ProjectHomeBase}\build\signtool.exe" sign /f "{#ProjectHomeBase}\build\something.pfx" /t http://timestamp.verisign.com/scripts/timstamp.dll /p 12345678 $f

[develar]

What problem do you have? Of course, you can set sign to custom function (see https://www.electron.build/configuration/win), but it is advanced usage. I think, it is not required for you.

[daffylumampao]

I already have a signtool.exe but I don't know where to put it on code. Is it like 'signingHashAlgorithms: SignTool=signname'?

[develar]

electron-builder does it for you. For what do you need to provide your own version?

[daffylumampao]

Oh. Ok I see. I just taught that signing must be done separately. So to clarify? Signing is already being done by electron-builder and so the setup.exe on your folder is already signed?

[develar]

Unlike other tools, electron-builder is a complete solution. Just provide cert (https://www.electron.build/code-signing) and that's all.

[daffylumampao]

@develar Is the certificateFile in win responsible for showing the digital signature tab on the .exe file?

[develar]

Yes. You can use or env to specify cert, or this option.

[daffylumampao]

May I ask how can you set it up in the env?

[develar]

Please see https://www.electron.build/code-signing