-o options, a FIPS-approved-algorithms mode, local/remote/dynamic SOCKS4/5 forwarding, forwarding-only sessions and negotiated-algorithm display; sessions using other OpenSSH options use OpenSSH automatically); RDP sessions through FreeRDP (NLA, certificate trust, fitted or fixed size, keyboard, mouse, text clipboard, Windows domains); raw TCP; Telnet terminal-type/window-size negotiation; RLogin with credential-backed user names and passwords; serial ports and format/flow/break controls.CSI ?33h, last-column wrap, CSI s/u, CSI 6n, clear-screen homes, CP437 symbols for control bytes, ANSI music ignored); a built-in 8×16 VGA bitmap font with seamless blocks and line drawing; terminal type ansi-bbs; RLogin with credential-backed user names and vault-stored passwords; Telnet binary mode both ways; BBS keys; Zmodem auto-start download and upload (CRC-16/32, error recovery, cancel, rename/overwrite/skip, partial-file cleanup); SyncTERM BBS list import with preview.This release does not implement every item in the comprehensive specification. The following are explicit limits:
.ans with SAUCE, ANSI-art viewer) are not included. TFTP supports octet mode, not netascii.Both platforms include the statically linked Lua worker; a separate Lua installation, LuaSocket or Python is not required for Lua scripts.
Linux uses distribution OpenSSH/Python/libssh and dynamically linked Qt libraries. The supplied .deb declares its actual dependencies and targets the build distribution.
The Linux build uses the distribution's FreeRDP 3 libraries for RDP.
Windows packages include Qt plugins/compiler runtimes, Python 3.14.10, libssh 0.11.3 with OpenSSL 3.5.9 and zlib 1.3.1 for the built-in SSH engine, FreeRDP 3.32.2 for RDP sessions, and portable OpenSSH tools. When Windows already supplies OpenSSH, the application prefers that system client. The bundled fallback is Microsoft's 10.4.0.0p1 Preview build; its preview status is retained here rather than described as a stable OS component. No SSH server service is installed. Users can replace the tools through an updated compatible distribution.
The Windows SSH diagnostic trace uses a private temporary directory and a regular file whose creation handle is released before OpenSSH starts. Failed trace creation reports an error before connection startup.
See TEST-RESULTS.md for the checks actually performed on this release.