mirror of
https://github.com/binaricat/Netcatty.git
synced 2026-11-22 08:03:40 +00:00
* Fix #919: harden built-in Telnet handshake for legacy gear The built-in Telnet client failed to advance past the welcome banner on some older switch firmware (HP ProCurve 2610 reported in #919) and, in the same session, leaked snippets of subnegotiation payloads into the terminal display as random-looking characters. Three independent correctness gaps in the old implementation, all rolled into one PR: 1. The negotiation parser was stateless per chunk. An IAC sequence split across TCP frames either dropped the lone IAC (lost command) or, for IAC SB...IAC SE blocks whose terminator landed in the next frame, fell through to "skip IAC SB and treat the rest as data" — spilling the subnegotiation payload (TERMINAL-TYPE strings, environment data) into the user's terminal as garbage. 2. The client was purely reactive — it only ever responded to options the server raised. Quite a bit of legacy equipment waits for the client to commit to SUPPRESS-GO-AHEAD / TERMINAL-TYPE / NAWS before it will continue past its banner, so connections silently hung at "Press any key to continue" forever. 3. Outbound user input was never IAC-escaped, so any 0xFF byte the user pastes (or that an alternate input encoding emits) would be read by the peer as the start of a command and eat the following byte. Approach: - New `electron/bridges/telnetProtocol.cjs` owns RFC 854 framing as a pure module. `createTelnetParser` is a stateful machine that buffers any partial command (lone IAC, IAC + verb, unterminated SB) across feeds and replays it once the rest arrives. Emits clean stream bytes, option commands and complete subnegotiations through callbacks. `escapeIacForWire` doubles 0xFF bytes on the way out with a cheap fast-path for the common (no 0xFF) case. - `terminalBridge.cjs` flips telnet handling into a lazy mode: until the peer sends an IAC byte the connection is plain passthrough, so raw-TCP-on-port-23 services are not corrupted by the protocol layer. Once the protocol activates, we proactively request DO SUPPRESS-GO-AHEAD, WILL TERMINAL-TYPE and WILL NAWS, and track those in a `requestedOptions` Set so the peer's acknowledgement does not trigger another reply (the classic negotiation loop). - TERMINAL-TYPE is now advertised as "XTERM-256COLOR" (upper-case); legacy boxes that case-sensitive-match termcap names recognise it. - Resize-driven NAWS subnegotiations now only fire after the protocol has actually activated, so a passthrough session is never poisoned. - Outbound writes for telnet sockets convert strings to UTF-8 buffers and run them through `escapeIacForWire`, so paste of binary content and non-ASCII input encodings round-trip safely. Tests: - 17 unit tests in `telnetProtocol.test.cjs` cover normal data, option commands, subnegotiation (including IAC IAC inside payload), every cross-frame split point (lone IAC, IAC + verb, mid-SB), the specific regression that previously leaked SB payload as data, ordering of data vs command callbacks, and the IAC escape helper. - Existing 18 telnet auto-login tests still pass, exercising the end-to-end socket → parser → renderer path. Full suite: 825 / 0 / 3. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * Address review: per-direction Telnet negotiation tracking RFC 858 §"Default Specification" treats WILL/WONT and DO/DONT as two independent option streams. The first revision of this PR used a single `requestedOptions` Set keyed by option byte, which incorrectly swallowed a peer's independent request on the opposite direction whenever we had our own request still pending for the same option. Concrete failure mode (highlighted by code review on the PR): we send `DO SGA` and the peer simultaneously sends `DO SGA` asking us to enable SGA on our outgoing side. The old check matched the peer's DO against our pending DO and returned silently, leaving the peer's request unanswered — strict implementations would either time out or proceed in the wrong mode. Fix: split pending requests into `pendingDoRequests` (we sent DO, awaiting WILL/WONT) and `pendingWillRequests` (we sent WILL, awaiting DO/DONT). Acknowledgement matching is now direction-aware; the peer's independent request on the orthogonal direction is treated as a fresh negotiation and replied to. While in there, the related bug uncovered by reviewing this code: when the peer's `DO NAWS` acknowledges our own `WILL NAWS`, we previously just dropped it on the floor — but the actual window-size SB payload needs to follow the WILL handshake either way (whether the DO is an acknowledgement of our WILL or an independent fresh request). The negotiator now always pushes the size subnegotiation on `DO NAWS`. Refactor: the negotiation policy lives in a new `createTelnetNegotiator` factory inside `telnetProtocol.cjs`, separate from the parser. That keeps `terminalBridge.cjs` thin and — more importantly — makes the policy directly unit-testable. 13 new tests cover the bidirectional-collision regression, the missing NAWS follow-through, fresh vs ack handling for each verb, the canonical handshake sequence, unsupported-option WONT/DONT replies, the TERMINAL-TYPE SEND→IS roundtrip, and the 80×24 fallback for invalid sizes. Total: 30 parser+negotiator unit tests, 18 existing telnet auto-login integration tests, full suite 838 / 0 / 3. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>