6 ms·
There have been recent changes in Microsoft's policy which now require a physical device to be used for signing. It's a giant pain. They alluded to cloud based
by caseymarquis 8y ago
There have been recent changes in Microsoft's policy which now require a physical device to be used for signing. It's a giant pain. They alluded to cloud based services for signing, but other than Symantec's Enterprise offering (no listed price on their site), this doesn't really exist. I think MS needs to step up and provide a simple cloud based signing service. They should have waited to do this before forcing these changes.
- electroly 8y agoInteresting, I just read up on that. Thanks for the info. My code signing certificate was issued before the cutoff, which appears to have been February 1, 2017. I guess I'm in for some fun when I need to renew.
- khedoros1 8y agoMy latest signing certs were issued around last August, and there didn't seem to be any extra rigmarole to get them (although I work for a large corporation; maybe that makes a difference?). We've basically got a giant keystore server that handles the secret keys for all of the company's signing, then signing provider plugins installed on the build machines to communicate with the keystore, while allowing us to use standard tools like signtool.
- Boulth 8y agoThat's not correct. Smart cards are required only by EV Code Signing certs. This is not it, this is regular code signing cert. And there is no reason to panic. While the author sees warnings now it's because the cert is fresh, it will gain reputation over time and be trustworthy. Just remember to timestamp while you sign!
- caseymarquis 8y agoEverything I've read hasn't differentiated. I can't seem to track down the official MS policy on my phone. Our certs are EV (need to sign drivers), so my experience is limited to EV certs.