SSH
A tabbed SSH terminal with saved connections and encrypted credentials.
You need a shell on the switch, and then on the next four switches, without five windows.
CySecTek
Sessions are tabs. Saved connections live in folders per site or customer, searchable, most recently used first. Authentication is a password or a private key — OpenSSH format, Ed25519, RSA or ECDSA, encrypted keys included — and any key already in ~/.ssh is offered on the connection form.
Host keys are pinned on first connect and a change is refused rather than shrugged at, with a panel that shows both fingerprints when a device has genuinely been rebuilt. Session transcripts can be written per host and are encrypted, because a switch session routinely prints running-config and SNMP communities.
What you walk away with
- Five switches as five tabs in one window
- Password or private key authentication, saved and encrypted
- A refused connection when a host key changes, not a dialog nobody reads
- An encrypted transcript of what was typed and what came back
Where it stops
Stated here rather than discovered on site.
- No SSH tunnelling, port forwarding or jump-host support. If you reach equipment through a bastion, keep the tool that does that.
- No SSH agent. Keys are read from a file; Pageant and ssh-agent are not consulted.
- PuTTY's .ppk format is not read directly — PuTTYgen exports an OpenSSH key that is.