From 3a7f12f0c37e691e1679dd6ee18ee963bd972143 Mon Sep 17 00:00:00 2001 From: George Christou Date: Fri, 12 Nov 2021 15:37:42 +0000 Subject: [PATCH] doc: [ssh] Use `%n` for ProxyCommand (#1696) --- .../content/docs/common-workflows/workflow-ssh-proxycommand.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/common-workflows/workflow-ssh-proxycommand.mdx b/website/content/docs/common-workflows/workflow-ssh-proxycommand.mdx index c9f9b1421..5e91f8537 100644 --- a/website/content/docs/common-workflows/workflow-ssh-proxycommand.mdx +++ b/website/content/docs/common-workflows/workflow-ssh-proxycommand.mdx @@ -19,7 +19,7 @@ Start by configuring a `Host` entry in `.ssh/ssh_config` for `localhost`: ```bash Host ttcp_* - ProxyCommand sh -c "boundary connect -target-id %h -exec nc -- {{boundary.ip}} {{boundary.port}}" + ProxyCommand sh -c "boundary connect -target-id %n -exec nc -- {{boundary.ip}} {{boundary.port}}" ``` The `ProxyCommand` tells the SSH client to invoke `boundary connect`. We are passing the `-exec nc` flag to