Repository navigation
Tether 0.10.3
Tether 0.10.3
Released 2026-11-06
Highlights
- Tether no longer crashes after it has been running for a long time and the network changes (for example when a VPN connects): finished background commands now give back the files they had open.
Fixed
- Each restart of a host's monitoring (after a reconnect, sleep, a network change or a changed refresh interval) left its connection's pipes open for good. After many of them Tether ran out of open files, and the next command crashed the app. Monitoring streams are now freed when they end, background commands close their pipes as soon as they finish, and running out of open files makes a command fail with a clear message instead of crashing.
- Programs started in terminals (shells, tmux, ssh, scp) no longer inherit Tether's own open files.
- A background command whose output was held open by a process it left behind (such as ssh's shared connection) could crash Tether when it was answered; it is now answered safely after a short wait.
- Password and host-key questions could stop appearing for the rest of the run after a passing error (such as too many open files); Tether now keeps listening for them.
- If the SSH config file could not be read for a moment, its hosts disappeared from the sidebar, and the next host edit could replace the file with an almost empty one. The hosts now stay, and Tether refuses to write a file it could not read (also in the config editor).
- A tab whose connection could not be started (too many files or processes open) no longer stays on "Connecting" for ever; it tries again in the usual rounds.
- A sign-in that Tether restarted because the network changed no longer counts as a failed sign-in, so a new tab is no longer closed after a flapping network.
- A file transfer that could not start its programs no longer leaves pipes open, and no longer risks crashing Tether.