Skip to content

Support SSH jump hosts / ProxyJump #141

Open

Description

@Aokoooooo

Motivation

I need to connect to a PC that is not directly reachable from the Internet and must be accessed through a VPS.

Conduit currently supports SSH agent forwarding, but that is different from using an SSH jump host. Agent forwarding allows a remote host to use the client key for onward authentication; it does not make Conduit connect to a destination through a bastion host.

Suggested behavior

Please add per-host jump host / bastion configuration equivalent to:

ssh -J user@vps user@pc

It would be useful to support:

  • Selecting another saved machine as the jump host.
  • Separate usernames, ports, and credentials for the jump host and destination.
  • SSH terminal and SFTP access through the jump host.
  • Host-key verification for both hops.
  • Clear separation between jump-host support and SSH agent forwarding in the UI.

If possible, please also document how jump hosts interact with Mosh. ProxyJump can carry the initial SSH bootstrap, but the subsequent UDP connection still needs a separately reachable network path.

Use case

Conduit → VPS → home PC → Herdr

This would make it possible to access home PCs, private-network machines, and development hosts without exposing their SSH ports publicly.

Activity

  1. gwitko commented on Jul 24, 2026

    @gwitko
    Owner

    We can add this. Thanks for the issue!

  2. self-assigned this
    on Jul 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions