Code signing policy

Route Map's Windows releases are to be signed with a Certum code signing certificate paid for and held by the maintainer.

Until signing is set up in the release workflow, Windows builds are unsigned, and the release notes of each unsigned release say so.

What is signed

Only routemap.exe and routemap-cli.exe from the Windows release of this repository, osintph/routemap, built by its public GitHub Actions workflow (.github/workflows/build.yml) on GitHub-hosted runners from a tagged commit of this public repository.

Never signed with this certificate:

Roles

RoleWho
Author (committer)osintph
Reviewerosintph
Approverosintph

Contributions from others reach the repository only through pull requests, reviewed by the maintainer, from contributors who have signed the Contributor Licence Agreement.

How a release is signed

  1. A release tag on this repository starts the build workflow on GitHub-hosted runners. It compiles, verifies and smoke-tests the Windows build and scans it with Microsoft Defender.
  2. The two executables are signed with the maintainer's certificate, and the signatures are verified (signtool verify /pa).
  3. The signed files are scanned again and published on GitHub Releases with a GPG-signed SHA256SUMS.

Account security

Multi-factor authentication is required for every account with write access to this repository and for the certificate account.

Contact

[email protected]. Security reports can be encrypted to the release key (RELEASE-KEY.asc).

Privacy

Route Map has no telemetry and no account. The online services it queries, and exactly what each receives, are listed in PRIVACY.md and in the app under Help > Privacy: CAIDA Hoiho (router hostnames), RIPEstat (public hop addresses and route details, and the user's public IP to find the origin when none is set), RIPE Atlas (anchor baselines; traces only with the user's own key), the user's own DNS resolver (reverse DNS), DB-IP (only for a download the user starts) and GitHub (only for an explicit update check).