Security
Reporting a problem
Please report security problems privately, through Security > Report a vulnerability on the repository, not in a public issue. Helpful: what an attacker could do, what they'd need first (a setup code, a computer's token, a ticket, being on the relay's network), and how to see it happen.
How Farpane protects you
- Nothing listens on the computer. Farpane connects out to your relay; no ports are opened on the computer or the router.
- Computers prove who they are with a random token; the relay keeps only its SHA-256.
- Opening a computer needs a ticket signed by the relay's secret, good for one minute. The relay's admin decides who gets one.
- Setup codes last 24 hours; ten wrong ones from one address block it for an hour.
- The person at the computer is told whenever someone has it open, and can stop it.
- Updates are signed. The app takes a new copy only if the update list carries the project's ed25519 signature, the file matches the list's SHA-256, and the list isn't older than one it already took.
- Releases are built in the open, by GitHub Actions from the source in the repository.
What it doesn't do (yet)
- The relay sees what passes through it. Connections are encrypted (TLS) between each end and your relay, but the relay itself handles the screen and keystrokes. Run it on a machine you trust. End-to-end encryption is planned, not done.
- On Windows it runs as the signed-in person, so it can't show or work the lock screen or administrator prompts.