Code signing policy
SignPath · pending
FanPilot has applied to the SignPath Foundation for free code signing. Once approved, releases will be signed as described below. Until then they are published unsigned, with a SHA256SUMS.txt to check every file.
Team roles
| Role | Who |
|---|---|
| Authors / Committers Trusted to change the source without additional review. | Mateus Conrad |
| Reviewers Review every change from people outside the team, such as pull requests. | Mateus Conrad |
| Approvers Approve each signing request, one release at a time. | Mateus Conrad |
Every team member uses multi-factor authentication for GitHub and SignPath.
How a release is built
- Releases are built only by GitHub Actions, from a version tag (vX.Y.Z) that must match the version in the source.
- The workflow runs the tests, the end-to-end tests and a smoke test of the zip before publishing.
- Signing will be requested from SignPath by that same workflow, and each request will be approved manually.
- Nothing will ever be signed on a personal machine.
What is signed
- FanPilot.exe, the program and service.
- FanPilotTray.exe, the tray icon.
- The Windows installer.
Third-party libraries (LibreHardwareMonitor and others) are shipped as their authors publish them.
Privacy: see the privacy policy.
Source code and release workflow: github.com/mateusconrad/FanPilot · release.yml