Relay 2.5.0
Relay 2.5.0
Share your phone's internet with your PC. Tap Start Sharing on
the phone, click your phone in the list on the PC, tap Allow.
That is the whole setup.
Everything runs between your two devices: no account, no server, no
telemetry. The connection is an encrypted WireGuard tunnel, and
every application on the PC goes through it -- not only the browser.
Download
| Platform | File | Requirements |
|---|---|---|
| Windows | Relay-Setup-x64.exe |
Windows 10/11. Per-user install, no admin prompt. |
| Windows (32-bit) | Relay-Setup-x86.exe |
Only if you know you need it. |
| Android | Relay-android-arm64-v8a.apk |
Android 8.0+, 64-bit ARM — almost every phone since 2017. |
| Android (any device) | Relay-android-universal.apk |
Same app, every CPU type. Larger. Use this if the one above says "app not compatible". |
| Android (stores) | Relay-android.aab |
Not directly installable. |
Install
- Install both apps.
- On the phone, turn on the hotspot -- or put both devices on the
same Wi-Fi -- and tap Start Sharing. - On the PC, open Relay. Your phone is already in the list. Click it.
- Tap Allow on the phone.
No camera on the laptop? The two-digit code works on its own. Prefer
the QR? It is still there.
Windows SmartScreen warns on first run because the installer is not
code-signed yet: More info -> Run anyway. See docs/release.md.
If Android says "App not installed", that one message covers
several unrelated causes. The two most common: an older copy built
from source is still installed (uninstall it first - a different
signing key blocks the upgrade), or Play Protect blocked the
sideload (Install anyway in its dialog).
docs/install-troubleshooting.md
covers the rest, starting with how to see the platform's real error.
Verify your download
SHA256SUMS.txt is attached.
sha256sum -c SHA256SUMS.txtPrivacy and security
- Nothing leaves your two devices. No accounts, no servers, no
telemetry, no analytics. - The tunnel is WireGuard. Its keys are minted for each pairing and
destroyed when sharing stops. - Keys are never broadcast. The phone announces only enough to be
found; the keys travel over a short exchange that you approve on the
phone, with the requesting computer's address shown. - DNS and IPv6 cannot go around the tunnel. While connected, Relay
blocks name lookups to any resolver but the tunnel's, and refuses
IPv6 outright because the tunnel carries IPv4 only. Without this, a
laptop sharing a Wi-Fi with the phone leaks the local ISP. - Nothing outlives the app. No system-wide setting is changed, and
those filters are destroyed by Windows the moment Relay stops -- even
if it is killed -- so a crash cannot leave you unable to browse.
Anyone on your network can see the phone is sharing and can ask to
pair -- that request is what the Allow prompt is for, so do not
approve one you did not start.
SECURITY.md
has the full threat model.
What changed
The readable version, written for people rather than for git, is in
the changelog.
Every commit in this release
- Write down 2.5.0 and 2.2.0, and correct a comment that had gone stale (#97)
- Stop claiming leak protection that is not there (#96)
- Stop redrawing two surfaces once a second for a change neither shows (#95)
- Close the two ways traffic went around the tunnel (#94)
- Stop paying the batch cost for every single packet (#92)
- List what Relay actually does, and what is still missing (#91)