Jump Host Support
Route a saved SSH connection through a configured jump host.
Availability
Partially implemented in stable. Read the limits below before relying on this workflow.
Reviewed against stable v0.5.1. Rust candidate additions are labeled separately. Release status.
The pain this solves
- Some SSH destinations are reachable only through a bastion or jump host.
What ships with it
- Maps a saved jumpHost value to OpenSSH -J.
- Imports ProxyJump from supported SSH config entries.
- Does not include the advertised hop diagram or per-hop credential editor.
Questions this answers
- Can a Chau7 SSH connection use ProxyJump?
- Does SSH config import preserve ProxyJump?
- Does Chau7 visualize a multi-hop SSH chain?
How it works
A saved SSH connection has a jumpHost field. When it is non-empty, Chau7 adds the value as an escaped argument to the ssh -J option.
The SSH config parser recognizes ProxyJump and carries that value into a manually imported connection. This covers the configured ProxyJump value used by OpenSSH.
The stable UI does not provide the advertised hop diagram, per-hop authentication controls, connection progress by hop, or ProxyCommand-specific chain management.
Why it matters
A saved ProxyJump value can keep a bastion destination with the SSH connection that uses it. OpenSSH remains responsible for the actual connection and authentication behavior.
Frequently asked questions
Does Chau7 pass ProxyJump to SSH?
Yes. A non-empty saved jump-host value is passed with the OpenSSH -J option.
Can I configure separate credentials for each hop in Chau7?
The stable connection model stores one target identity-file path and a jump-host string; it does not expose a per-hop credential editor.
Does it support ProxyCommand chains?
The documented stable path is ProxyJump. Do not rely on a Chau7-managed ProxyCommand chain UI.