CODE SIGNING POLICY

How releases are built, approved and signed, and what the program does with your data.

Status: the releases published so far are not code-signed. The project meets the conditions for the free open source signing programme of SignPath Foundation and is applying to it. The rules below are the policy that applies once signing is active; this page will say so when it is.

Attribution

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

Signed files show SignPath Foundation as the publisher: in Explorer, right-click RoboXCopy.exe, choose Properties, tab Digital Signatures. The program itself is written and maintained by Cristian Castellari (see below), not by SignPath Foundation.

What is signed

How a release is made

  1. Changes are committed to the public repository. The build script and the release workflow (.github/workflows/release.yml) are part of that source and are reviewed like any other change.
  2. A version tag (vX.Y.Z) starts the release workflow on GitHub-hosted runners: tests, build, checksum.
  3. The workflow sends the unsigned RoboXCopy.exe to SignPath, which checks that it comes from this repository's automated build.
  4. The approver below approves each signing request manually.
  5. The signed file is published as a GitHub release together with its SHA-256 and a GitHub build attestation (gh attestation verify RoboXCopy.exe --repo Skyflash/RoboXCopy).

Roles

RoleWhoWhat they do
Authors (committers)Cristian CastellariWrite the code and the build scripts.
ReviewersCristian CastellariReview changes proposed by anyone who is not a committer.
ApproversCristian CastellariApprove every signing request.

All team members use multi-factor authentication on GitHub and on SignPath. If more people join, they are added here.

Privacy policy

This program will not transfer any information to other networked systems unless specifically requested by the user or the person installing or operating it.

Reporting a problem

If you think a signed file is not what this policy describes, tell us on GitHub issues; we will investigate and help find the root cause. SignPath Foundation can also be reached at support@signpath.io.