No idle timeout on established gate tunnels #81

New issue

Open

opened 2026-08-22 10:59:44 +00:00 by a73x · 0 comments

a73x commented

2026-08-22 10:59:44 +00:00

(Migrated from git.a73x.sh)

From the pre-launch security audit (finding GATE-4, ranked #5 of the outstanding set).

Established gate tunnels have no idle timeout. The per-connection handshake defense is
already good (30s handshakeGrace), and concurrent unauthenticated handshakes are now
bounded (MaxStartups, shipped). What remains is that an AUTHENTICATED tenant can hold
idle tunnels open indefinitely, which compounds the connection-exhaustion surface rather
than standing alone.

Fix. An idle deadline on the established tunnel. Low; authenticated-tenant only.

Migrated from git-collab issue 9a7edf8108ed7dffffa87ed72a11e98d742bf9b3.

Original author: a73x dev@a73x.sh.

From the pre-launch security audit (finding GATE-4, ranked #5 of the outstanding set). Established gate tunnels have no idle timeout. The per-connection handshake defense is already good (30s handshakeGrace), and concurrent unauthenticated handshakes are now bounded (MaxStartups, shipped). What remains is that an AUTHENTICATED tenant can hold idle tunnels open indefinitely, which compounds the connection-exhaustion surface rather than standing alone. **Fix.** An idle deadline on the established tunnel. Low; authenticated-tenant only. --- Migrated from git-collab issue `9a7edf8108ed7dffffa87ed72a11e98d742bf9b3`. Original author: a73x <dev@a73x.sh>.