docs: deferred Windows code-signing build-out plan#23
Merged
Conversation
Tracking doc for Authenticode/SmartScreen code signing, deferred until revenue justifies the annual cert cost. Covers the options (Azure Trusted Signing / OV / EV via cloud HSM), the post-2023 hardware-key requirement, Tauri + CI wiring steps, and an explicit note not to confuse this with the existing minisign updater signing.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Tracking doc (docs/windows-code-signing.md) for Authenticode / SmartScreen code signing — deferred until revenue justifies the annual cost.
Covers:
$120/yr), OV via cloud HSM ($200–400), EV (~$300–700)bundle.windows(signCommand/certificateThumbprint + timestamp) + CI wiring stepssigntool verify /pa /v) and a checklistNo code/behavior change — documentation only.