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

Aberta
#89 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 3 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Funcionalidade
Clareza
Claramente especificada
Status de atividade
Pouca atividade
Stack de tecnologia
azure, github-actions, python
Domínio
devops, release, security

Direção de pesquisa

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

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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".
Linguagem predominante
Python
Estrelas
0
Forks
2
Merge médio
2d 13h
PRs com merge (30d)
2

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de TMHSDigital/autoclicker

Todas as issues de TMHSDigital/autoclicker

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.