AFK4.NET

Code signing policy

How AFK4.NET software is signed and who is responsible.

Free code signing provided by SignPath.io, certificate by SignPath Foundation.

What is signed

The AFK4.NET installer and the MSI packages of its parts (AFK4.NET Agent service, player screen, Panel, setup wizard), built by GitHub Actions from the open repository. We do not sign anyone else’s software.

Who is responsible

Committers and reviewers
Repository members with write access. Outside contributions are reviewed by a member before merging. github.com/MubiZero/afk4.net/graphs/contributors
Approvers
The project owner, who approves every release for signing by hand. github.com/MubiZero

How a release gets signed

  1. Every change passes required CI checks; nothing merges into main without a green run.
  2. GitHub Actions builds the packages from this repository’s source code.
  3. The project owner approves each signing request by hand in SignPath.
  4. All members use multi-factor authentication on GitHub and SignPath.

Privacy

The software sends data only to the AFK4.NET server the club uses, and only to run the club. The privacy policy lists exactly what. Privacy