build: switch to cloud code signing for Windows #9948
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The requirements for Windows code signing changed in 2023, so that newly generated certificates can only be stored in hardware modules. Luckily, I managed to snag a three year certificate before that so it hasn't affected us so much. Now though, it does, because our cert is expiring in March.
This changes the code signing process for Windows to use a cloud service, Azure Trusted Signing. This appears to work equally well and outsources the problem entirely, while also being cheaper than the actual certificate was to begin with. 🤷
The signing entity will be Kastelo AB and not the Syncthing Foundation, because the latter is almost impossible to get a certificate for as it's not a normal corporate entity whose existence can be verified, etc. This is also how it was prior to the latest certificate; it's not ideal, but I think it's acceptable under the circumstances.