Code-sign releases with Azure Trusted Signing to remove the SmartScreen warning
维护者通常 3 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
调研方向
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 内容生成。
描述
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
- Set up Azure Trusted Signing: identity validation, a certificate profile, and a service principal scoped to signing.
- 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. - Verify the signature in CI (
signtool verify /pa) before publishing. - Fund it: the monthly cost is a good concrete sponsorship goal ("Help us sign releases"), see the sponsorship issue.
- 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
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
TMHSDigital/autoclicker 的其他 Issue
-
maintenance priority: low
难度 3/5 半天 新手友好度 56/100
TMHSDigital/autoclicker#202 ·
维护者通常 3 天内回复
-
bug priority: low
难度 3/5 1-2 天 新手友好度 52/100
TMHSDigital/autoclicker#201 ·
维护者通常 3 天内回复
-
dependencies maintenance priority: medium
难度 5/5 一周以上 新手友好度 35/100
TMHSDigital/autoclicker#154 · 1 条评论 ·
维护者通常 3 天内回复
-
marketing packaging priority: low
难度 4/5 3-5 天 新手友好度 38/100
TMHSDigital/autoclicker#118 · 1 条评论 ·
维护者通常 3 天内回复
-
documentation marketing priority: medium
难度 3/5 1-2 天 新手友好度 55/100
TMHSDigital/autoclicker#117 · 1 条评论 ·
维护者通常 3 天内回复
查看 TMHSDigital/autoclicker 的全部 Issue
相似的 Issue
-
hive size:simple
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
A new VOLTTRON_HOME starts with agent isolation mode on (string comparison of a boolean default)未关闭
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 2/5 1-3 小时 新手友好度 70/100
painted-porch/marcus#977 ·
维护者通常 1 天内回复
-
llm translation
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
FAIRmat-NFDI/sand#239 ·
维护者通常 1 天内回复