dtssh lets you ssh into any machine through a
Microsoft Dev Tunnel —
across NAT and firewalls, with no SSH keys, passwords, or host-key prompts to
set up. It runs a dedicated SSH server on the host (reachable only through the
tunnel) and auto-configures the client, so plain ssh, scp, git, and
VS Code Remote-SSH just work.
Both machines only need to be logged into the same devtunnel account.
# Linux / macOS
curl -fsSL https://raw.githubusercontent.com/bmiddha/devtunnel-ssh/main/scripts/install-release.sh | bash# Windows, or anywhere with PowerShell 7+ (also macOS/Linux)
irm https://raw.githubusercontent.com/bmiddha/devtunnel-ssh/main/scripts/install-release.ps1 | iexThis downloads a prebuilt binary from the latest
GitHub Release. You also
need OpenSSH (ssh; plus sshd on Linux/macOS hosts). On Windows, dtssh
downloads a pinned portable Win32-OpenSSH build on first host startup. The
devtunnel CLI is auto-downloaded on first use.
On the host (the machine you want to reach):
dtssh login # sign in once (opens a browser)
dtssh host # start hostingOn the client (the machine you connect from):
dtssh login # same account as the host
dtssh discover # finds the host, sets up `ssh dt-<host>`
ssh dt-<host> # doneThat's it. scp, git, rsync, and VS Code Remote-SSH work against the same
alias.
Keep a machine reachable without leaving a terminal open (starts at login, auto-restarts, no admin needed):
dtssh service install
# Or, use a specific tunnel:
dtssh service install --tunnel <tunnel-id>
dtssh service status # or: logs, restart, stop, start, uninstallInstallation accepts similar flags as host: --port, --user, --alias,
--tunnel, --expiration, --system-sshd,
and --no-wsl-boot (opts out of the WSL Startup launcher).
Services always use persistent mode: --persist is accepted for compatibility,
but is redundant. Setting --persist=false (or 0, no, or off) is rejected.
Unknown options, unexpected arguments, and missing option values are rejected.
| Command | What it does |
|---|---|
dtssh login |
Sign in to devtunnels (flags pass through, e.g. -d device code). |
dtssh host |
Expose this machine and publish discovery info. |
dtssh discover |
Find hosts and wire up ssh <alias> (the only pairing step). |
dtssh service … |
Run the host as a background service (install/status/logs/…). |
dtssh list |
List configured host aliases. |
dtssh remove <alias> |
Remove a host alias. |
dtssh doctor |
Check your environment. |
Run dtssh <command> --help for options. Set DTSSH_DEBUG=1 for diagnostics.
dtssh host starts a hardened sshd bound to loopback and hosts that port over
a dev tunnel in-process via the
Dev Tunnels SDK. It publishes pairing
info (alias, host key, and an ephemeral key seed) in the tunnel's account-private
description. dtssh discover reads that, installs the key, pins the host key, and
adds an ssh_config alias whose ProxyCommand (dtssh proxy) pipes SSH straight
into the tunnel.
So ssh <alias> does normal SSH public-key auth over the tunnel — "no extra
auth" means dtssh provisions the key for you, not that SSH auth is disabled. The
tunnel is the only ingress, and the host key is pinned (no trust-on-first-use),
so the relay can't MITM the connection.
Requires the .NET 10 SDK; dtssh is a
single self-contained NativeAOT binary.
dotnet publish -c Release -r linux-x64 -p:PublishAot=trueRun the dependency-free host shutdown regression checks with the .NET 10 SDK:
dotnet run --project tests/HostShutdown/HostShutdown.csproj -c ReleaseEach scenario runs in a child process so checks include the real process-exit callbacks. No Dev Tunnel, SSH server, or sign-in is needed.