Tephro · Guides
Code signing policy
Tephro's Windows files are code-signed so that Windows can tell they come from this project, unchanged. Free code signing provided by SignPath.io, certificate by SignPath Foundation. Releases made before the certificate arrived are unsigned, and Windows warns about an unknown publisher for those.
What is signed
Only files built from this repository's source:
| File | What it is |
|---|---|
Tephro Setup <version>.exe | The Windows installer |
tephro.exe | The desktop client |
tephro-appaudio.exe | The helper that captures one application's sound for a stream |
tephro_vcam.dll | The virtual camera that carries a shared screen into the client |
tephro-<version>-windows-amd64.exe | The server, for Windows |
The files from upstream projects that ship inside the installer, Electron's and Chromium's libraries among them, are not signed with this project's certificate.
Every signed file is built by the project's GitLab CI pipeline from a tagged commit of the public repository, and each release is approved by hand before it is signed. The build scripts and the CI configuration are part of that repository and are reviewed like any other change.
Team roles
- Committers and reviewers: members of the Encenillo group. A change from anyone else arrives as a merge request and is reviewed by a committer before it is merged.
- Approvers: the members of that group with the Owner role, who approve each release for signing.
Every team member signs in to GitLab and SignPath with two-factor authentication.
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.
In practice, the client connects to the Tephro servers you add and to nothing else on its own:
- The update check is off until you turn it on. Choosing a frequency in Settings → Desktop → Check for updates, or clicking the update button on the left, asks GitLab's public list of Tephro releases for a newer version. The request carries nothing about you or your servers.
- Link previews in channels are fetched by the server, not by your client. In a direct message, your own client fetches a preview of a link you send.
- A video player from another platform loads only when you click play on its card.
The server is run by whoever operates it. On its own it connects to nothing but what its members and its operator ask for:
- Link previews in channels: when a member posts a link, the server fetches its title and picture (
link_previews, on unless the operator turns it off). - Only when the operator asks: its update check (
update_check_every, off until set), a certificate from Let's Encrypt when a domain is set, and the list of VPN address ranges and a lookup of its own public address, each from an admin command.
What Tephro keeps on your machine, and what it never stores, is in Privacy. The Windows installer shows this privacy note before it installs.
Checking a signature
In Windows, right-click the file, open Properties → Digital Signatures, and check that the signer is SignPath Foundation. Every release also lists its files in SHA256SUMS, signed with the maintainer's OpenPGP key; the server guide shows how to check it.