Code-sign releases with Azure Trusted Signing to remove the SmartScreen warning

未关闭
#89 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 3 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
冷清
技术栈
azure, github-actions, python

调研方向

Start with docs/RELEASING.md and locate the release job that builds the PyInstaller executable, then review its checksum and publishing steps. Set up Azure Trusted Signing with OIDC, add signing and signtool verify /pa before publishing, and update the README, landing page FAQ, and RELEASING.md. Done means published executables have a verified Authenticode signature and the docs no longer tell users to click “Run anyway.”

由索引模型根据 Issue 内容生成。

描述

packaging priority: medium security

Why it matters

Every new user hits "Windows protected your PC" on first run, and many stop there, especially for an input-automation tool, which antivirus heuristics already treat with suspicion. Now that the app is on Scoop, about to be on winget (#76), and has a landing page (#77), the SmartScreen warning is the biggest remaining barrier between a visitor and a working install. The checksum and provenance attestation help experts but not typical users.

Evidence

  • docs/RELEASING.md, "Code signing": signing was deferred, with Microsoft Trusted Signing (Azure) named as the first choice; SignPath's free open-source program is unavailable because of the CC BY-NC license (decided in #71).
  • The README and landing page both carry SmartScreen instructions.

Suggested approach

  1. Set up Azure Trusted Signing: identity validation, a certificate profile, and a service principal scoped to signing.
  2. Add a signing step to the release job between the PyInstaller build and the checksum, using azure/trusted-signing-action (pinned SHA) with OIDC federated credentials, so there's no long-lived secret.
  3. Verify the signature in CI (signtool verify /pa) before publishing.
  4. Fund it: the monthly cost is a good concrete sponsorship goal ("Help us sign releases"), see the sponsorship issue.
  5. Update README, landing page FAQ and RELEASING.md once releases are signed.

Done when

  • Release executables are Authenticode-signed with a verified publisher, the signature is checked in CI, and docs no longer tell users to click "Run anyway".
主要语言
Python
星标
0
派生
2
平均合并
2 天 13 小时
30 天内合并 PR
2

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

TMHSDigital/autoclicker 的其他 Issue

查看 TMHSDigital/autoclicker 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。