Add built-in code signing to ScITE?

[emendelson]

In order to codesign a script while compiling it, it's possible to add a command to the Run After tab, but when I do this, I always have to switch manually to the box where Windows asks for permission to run the program. This is only an inconvenience, but other IDEs make the process smoother by including a built-in option to specify a code-sign command so that you don't have to switch focus and click a box. An example of this is InnoScript Studio for compiling InnoSetup installation scripts.

Is there any hope that this could be include in ScITE in the future? I'm already so grateful for what ScITE does that I'm perfectly happy with what I have now, but I hope this might be a useful addition.

[steve8tch]

Yes - you can build this into the compile flow in Scite. Here is an example that we use

#AutoIt3Wrapper_Run_After=c:\Windows\signtool.exe sign /sha1 <Your Certificate HASH> /t http://timestamp.comodoca.com "%out%"

Hope this helps

[emendelson]

@steve8tch That works perfectly. Thank you. Instead of running signtool.exe, directly in the Run After field, I had been using a compiled AutoIt executable that runs the signtool.exe command with the required parameters, and the workflow got interrupted by the prompt asking me to run the file. Your solution avoids the interruption. Thank you again.

Edited January 10, 2023 by emendelson

[blumi]

I have found this here, cause I want to sign my exe after compiling. 

But it does not work, maybe I do something wrong, who can help?

I got my codesign certificate to my local computer and want to use this

So I did copy the thumbprint of the certificate to the <Your Certificate HASH>

#AutoIt3Wrapper_Run_After=c:\Windows\signtool.exe sign /sha1 123454332example12343 /tr http://timestamp.sectigo.com

I tried /t /tr both did not work, I tried it without the time option, nothing happens

Is it possible to see some errors of the signtool?

 

What is this "%out%" for? 

Edited January 21 by blumi