Code signing policy
When the installers on GitHub Releases are signed, every signed file will be built by the Desktop build workflow in GitHub Actions, from the tagged commit of the public source, and from nothing else: no file built on someone’s own computer is ever signed.
Team roles
Section titled “Team roles”| Role | Who |
|---|---|
| Committers and reviewers | Members of the periskopos organization |
| Approvers | Owners of the periskopos organization |
Today that is one person, Daniel Noam Tuby, in every role. Every change to the code that handles keys, AI assistants, releases and CI is reviewed by an owner (the repository’s CODEOWNERS), and each signing request is approved by an owner before it’s signed. Everyone in these roles uses multi-factor authentication for GitHub and for the signing service.
Privacy
Section titled “Privacy”This program will not transfer any information to other networked systems unless specifically requested by the user or the person installing or operating it.
What it connects to, and what it never sends, is in Privacy.
Installing and removing it
Section titled “Installing and removing it”Getting started covers installing, and Uninstalling covers removing it and what it leaves behind.