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

オープン
#89 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 3 日以内に返信

まだ誰も着手していません。

評価

難易度
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時間
マージ済み PR(30日)
2

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

TMHSDigital/autoclicker のほかの issue

TMHSDigital/autoclicker の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。