#125 Windows code signing — or disclose the unsigned status

[Anonymous]

Originally created by: kristofferR

Releases sign and notarize macOS and sign the updater, but there's no Windows Authenticode step, and nothing in the README or landing discloses it — first-run Windows users hit an unknown-publisher SmartScreen wall with no explanation. Options in cost order: (a) a one-line "Windows builds are unsigned for now; here's why and what to click" note in README/landing — costs nothing; (b) Azure Trusted Signing (cheap for open source); (c) winget distribution, which also builds reputation.

[Anonymous]

Originally posted by: kristofferR

Addressed in [#137]: the README now discloses that Windows builds are currently unsigned and may trigger a SmartScreen "Unknown publisher" warning, satisfying the "disclose the unsigned status" path.

Note: the same disclosure still needs to be added to the localized landing page — that copy was deferred to a re-localization pass after the 10-language localization in [#138], tracked alongside [#127].

[Anonymous]

Ticket changed by: kristofferR

• status: open --> closed