TetherBay 0.2.411
· Updated 2026-08-02
TetherBay 0.2.411 packages the latest documented beta improvements across relay resilience, network fallback, storage, and encrypted sync.
Highlights
- Windows upgrades now retire even an already-running legacy beta updater.
Setup disables and removes the old scheduled task, terminates its active PowerShell/VBS process tree, and refuses to continue if the obsolete LocalAppData application copy cannot be removed. This closes the race that could restore and launch an old beta one second after a successful Program Files installation while preserving settings and synced folders.
- Windows one-line upgrades now complete cleanly over running beta clients.
The PowerShell flow downloads a recognisably named installer, closes existing launcher and agent processes, waits for setup to finish, verifies the installed binary version, and explicitly opens the matching launcher from Program Files. The release packager also rejects stale launcher or agent payloads whose FileVersion does not match the installer version, so a current filename cannot conceal old application bytes.
- Sync server no longer slows down as the total number of synced files grows.
The relay's metadata store became database-authoritative: per-write work is now proportional to what actually changed (indexed point/range queries) instead of the whole dataset, and the server no longer loads all records into memory at startup — so boot time and memory stay flat as the service grows.
- One busy account can no longer degrade everyone else.
Write contention is now keyed per folder/account behind a new lock manager (opt-in sharded mode), with a fair-share soft throttle that *slows* an over-active tenant rather than blocking it, and per-tenant lock metrics on /metrics. Closes the single-account denial-of-service path that could previously wedge the whole relay.
Fixes
- Windows upgrades now retire even an already-running legacy beta updater. Setup disables and removes the old scheduled task, terminates its active PowerShell/VBS process tree, and refuses to continue if the obsolete LocalAppData application copy cannot be removed. This closes the race that could restore and launch an old beta one second after a successful Program Files installation while preserving settings and synced folders.
- Windows one-line upgrades now complete cleanly over running beta clients. The PowerShell flow downloads a recognisably named installer, closes existing launcher and agent processes, waits for setup to finish, verifies the installed binary version, and explicitly opens the matching launcher from Program Files. The release packager also rejects stale launcher or agent payloads whose FileVersion does not match the installer version, so a current filename cannot conceal old application bytes.
- Sync server no longer slows down as the total number of synced files grows. The relay's metadata store became database-authoritative: per-write work is now proportional to what actually changed (indexed point/range queries) instead of the whole dataset, and the server no longer loads all records into memory at startup — so boot time and memory stay flat as the service grows.
- One busy account can no longer degrade everyone else. Write contention is now keyed per folder/account behind a new lock manager (opt-in sharded mode), with a fair-share soft throttle that *slows* an over-active tenant rather than blocking it, and per-tenant lock metrics on /metrics. Closes the single-account denial-of-service path that could previously wedge the whole relay.
- PostgreSQL is now a supported metadata backend for the relay (selectable by configuration), alongside the existing SQLite store which remains the default for local and self-hosted use. Includes a one-shot SQLite→Postgres data migration tool with row-count reconciliation.
- Cloudflare R2 (S3-compatible) blob storage is production-ready. The relay can store encrypted blobs in R2 with presigned zero-egress downloads, a live storage health/deep-probe check, and a global storage-cap safety valve; switching is a configuration change. Verified end-to-end against a real S3 server.
- Server startup no longer waits on the boot-time storage maintenance pass. The audit that repairs/cleans staged and orphaned blobs now runs after the server is listening instead of before it binds, so health checks come up immediately even on an object-store backend where that pass can take minutes. Controlled by TETHERBAY_STARTUP_AUDIT_MODE (background default, off to skip at boot, blocking for the legacy pre-bind behavior).
- End-to-end encryption for synced folders and clipboard. File contents are encrypted on the sending device with AES-256-GCM (framed streaming AEAD) before upload; folder keys are shared device-to-device via sealed ECDH envelopes and never reach the relay. Clipboard items are sealed per-event with the account key. The relay stores ciphertext only and has no decryption path. Rollout is fail-closed — uploads are held rather than sent in the clear if any device in a folder cannot yet support E2E, so every device in a folder must be updated before content flows again. Clipboard E2E defaults ON since 2026-06-15.
- Remote file access hardened alongside folder encryption.
Known issues
- macOS beta packages are unsigned and not notarized; follow the documented Gatekeeper first-launch steps.
Availability
- win-x64 — Download
0b32191e7c5ee14f3272682e3dcfbd4073724f30fc4d52263d6864dd3748d19d - osx-arm64 — Download
2996c938b78c7932389c304c317af77a9af9e5fa897660ff2fbd6e5606c3f2bc - osx-x64 — Download
65ed3d114be69168a829cae6d100240f6b0c314005de7ccc66cbc8e624e29313 - linux-x64 — Download
6bbb7bd8d0cbaf8668722c4775bb9a455607aa1a59b38623d063200a870a3395 - linux-arm64 — Download
ab16436589c938c12230972d2455b36124a733940d0cf346f7d8573d188999c0 - android — Download
d9e9f0b582384c5a69d74c1028562c8b6d612141d383c7a78b017c85a7a43420 - ios — pending