fix(telnet): accept full reads and bound negotiation replies #120
Loading…
Reference in a new issue
No description provided.
Delete branch "codex/nvt-rfc-boundaries"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
A valid 16 KiB Telnet read exceeded the old pending buffer. A valid 40-character terminal name could overrun the reply buffer. The client now accepts complete reads, bounds incomplete subnegotiation, validates terminal names and reply capacity, and sends suboption replies only after negotiation enables the option.
Validation: 1,087 offline tests pass after rebase onto released v0.10.15. The exact revision passes all nine native pub400 System Request checks, including Save, Restore, Cancel Invite, and execution of retained input. The transfer evidence suite is also run before release. Documentation records RFC and pinned implementation comparisons, the v0.10.15 release, and explicit limits. No ACS parity claim or TN3270E support is added.