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

Ouverte
#89 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 3 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
48/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
Calme
Stack technique
azure, github-actions, python
Domaine
devops, release, security

Piste de recherche

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.”

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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".
Langage dominant
Python
Étoiles
0
Forks
2
Merge moyen
2 j 13 h
PR mergées (30 j)
2

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de TMHSDigital/autoclicker

Toutes les issues de TMHSDigital/autoclicker

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.