So I just got an expiration notice from Sectigo that says I’m expired. 3 years sure went by fast! I paid $798 for 4 years (they still owe me a year I think, so I’m contacting them). Anyway, a year is now $714. That seems like a lot. I guess the new Setupbuilder will be able to use the new Microsoft signing (soon I guess)? Anyone have experience with that yet?
Hi,
It seems to work already, see this post from Jane: My first look at SetupBuilder 2025
Friedrich has done a lot of work to be able to use almost any Code Signing method out there.
Regards
Johan de Klerk
I wonder how hard it is to set ones self up as a certificate authority in order to print money?
Using Microsoft Azure code signing is very easy to use - thanks to @MarkGoldberg for this article:
Microsoft Trusted Code Signing - Steps to set it up - Nicht kategorisiert - ClarionHub
I’ve set up Azure code signing about 5 weeks ago and it’s working perfectly.
I do not use SetupBuilder. I use InstallMate. I asked the support at InstallMate to implement Azure code signing a few weeks ago and they’ve now finished it so I can nativley use Azure code signing with my favorite installer tool.
Jens
Ray, I have been using the new Microsoft Trusted Code Signing in SetupBuilder since Friedrich added support for it.
It works flawlessly.
Charles
Yes Azure Trust Signing is a cost-effective option, but the verification process is quite complete, and most of the time it takes so many days to clear the pending status! And of course, after token storage, code signing certs become costly, but I am using Sectigo Code Signing from SignMyCode at $219 per year, and it works fine. You can check and take the best decision from your end!
FWIW I used the Microsoft Authenticator app and completed the authentication in minutes.