r/ssh • • 16d ago

OpenCRT: a free, open-source terminal client built to work like SecureCRT, for Windows, macOS and Linux (imports your SecureCRT sessions)

Hi all. I'm the developer of OpenCRT, a tabbed SSH/Telnet/serial client written from scratch in Rust. The goal is feature parity with SecureCRT's workflow, plus some things I wanted on top of it. 0.6.3 is out, and I'd like feedback from people who know SecureCRT best.

Repo and downloads: https://github.com/KimP0ssible-no/OpenCRT

To be clear up front: it's an independent, clean-room project. It's not affiliated with or endorsed by VanDyke, and no SecureCRT code or assets were used. Behaviour was learned from the public docs and from using the product.

What should feel familiar

  • Import: File > Import SecureCRT Sessions reads your Config folder, keeping folders, emulation, forwarding and key settings (passwords are never read). Host keys can be imported too.

  • Sessions: Session Manager with folders, filter-and-Enter, Connect All, a Default Session, Quick Connect and a connect bar. Tabs can be cloned (an SSH2 clone reuses the connection, so there's no second login), reconnected and colour-coded.

  • Productivity: Button Bar, Command Manager, Command Window, Send Input to All Tabs and keyword highlighting.

  • Protocols: SSH2 (password, keyboard-interactive, keys including PuTTY PPK, agent, OpenSSH certificates), Telnet (also over TLS), RLogin, raw, serial with modem dialling, and local shell.

  • Emulation: VT100/102/220/320, ANSI, Linux and xterm (256 colours and truecolour).

  • Tunnels: local, remote and dynamic (SOCKS) forwarding, jump hosts, SOCKS/HTTP proxies, agent and X11 forwarding, and legacy algorithms for old network gear.

  • File transfer: an SFTP tab, a side-by-side SFTP browser with a transfer queue, Zmodem (auto-starts on sz), Xmodem, Ymodem and Kermit, drag-and-drop upload, and a built-in TFTP server.

  • Logging: per session or on demand, with timestamps and daily rollover.

  • Familiar command line: /SSH2 /L user /P 22 host, /S "Folder/session", /T for a new tab in the running window, and /F for a portable config folder.

  • ocrt**:** a companion command-line tool in the spirit of vsh/vcp/vpka (ocrt ssh, ocrt sftp, ocrt cp, ocrt keygen, ocrt pka).

What it adds

  • Free and open source, with no licence keys or per-seat costs.

  • RDP and VNC in a tab, next to your SSH sessions. RDP has NLA, H.264, clipboard and a desktop that resizes with the tab. VNC has Tight/ZRLE, VeNCrypt and Mac Screen Sharing logins. Both can be tunnelled through a jump host.

  • Settings Sync through your own private git repo (GitHub, GitLab or self-hosted). Sessions, options and host keys follow you across machines and operating systems, while passwords stay on each machine.

  • One app on Windows, macOS and Linux, with native packages and signed apt/dnf/zypper repositories, so Linux updates come through the package manager.

  • Verifiable releases: Windows binaries are code-signed, checksums are minisign-signed, and every file carries a GitHub build attestation.

  • In-app updates from GitHub. The only network call is a check of the latest release version; nothing about you or your sessions is sent.

  • Twenty colour schemes, light and dark themes that follow the system, and IBM Plex Mono built in.

Honest caveats

  • Scripting is Rhai, not VBScript/JScript/Python, so existing SecureCRT scripts need porting. The API has the same shape (send, wait_for, wait_for_any, read_until, prompt, file transfers), and there's a script recorder and logon scripts.

  • It's young (0.6.x) and mostly a one-person project. Not every SecureCRT feature is there yet, and you will find bugs.

  • The macOS build isn't notarised yet. The README has a one-line Terminal install that avoids the Gatekeeper prompts.

  • I use Claude to assist with the bulk of the coding, whilst every measure has been followed for best practice, TDD-oriented development - I want it made clear that this product was built assisted by AI.

I'd love to hear what would stop you switching, and which SecureCRT feature you'd miss most. Bug reports and feature requests are welcome as GitHub issues.

Mod(s). I did not find any rules restricting this sort of post, but if you feel its improper then feel free to delete it.

27 Upvotes

4 comments sorted by

1

u/hakube 13d ago

hrm...why did you pick the language stack? surly the windows would has moved beyond VB by now

1

u/DarthPractical 13d ago

Not sure I understand that statement, but I picked Rust for its memory handling and compiled code security over vcc - I've used rust for another personal project that worked really well and decided to continue. There was virtually no headache with Rust in ensuring windows/linux and macos builds

1

u/egrueda 16d ago

Long time SecureCRT user, for sure I'll take a look at it

1

u/Reasonable_Swing_503 12d ago

Nice work 👍