So my Code sign is expired thanks to Sectigo ripping me off for a full year… and not replying when I pointed it out on the invoice that is on their site.
Anyway, I just want to test the program (we use it as well), so I wanted to make an install. In the setup I told it not to use code signing but it fails anyway. Any idea’s? I’m getting a compiler error gen 1053 code signing failed error 2.
I guess I better look into the Microsoft thing with more intention.
Thanks,
Ray
It’s been a while since I’ve built an installer, Ray.
But remember that you may have set code-signing in multiple places in your script - for the installer itself and also to code-sign individual files that you’re installing. Make sure you’ve disabled all of those if you’re getting an error.
I’ve been using Microsoft code-signing for more than a year and a half and it’s been solid.
Thanks Jane. That was it. I forgot I had all those code signs in my script. I know that they were irrelevant.. or at least I think they were because the one in setup overrode those signings. I’m going to dig into the MS code signing. Sectigo has gone off the rails. They didn’t send the USB signing that I had already paid for, so wanted me to buy a year, then they would add a year to that. I told them they should give me a year because they messed up. I’m expecting a call.. we’ll see what happens. Either way, I’m not doing business with them anymore… I’ll build my own code signing company if that’s what it takes (just kidding, way too much work).
Ray,
The code sign statement(s) in the script is usually what signs the program EXE itself.
The part in the installer about code signing controls signing the installer itself.
Typically you need/want both because the installer needs to be code signed for a proper trusted installation and your program needs to be code signed so that the user (and system) trusts it when it runs.