Skip to content
This repository was archived by the owner on Jan 22, 2025. It is now read-only.

Commit 5565a84

Browse files
committed
Moved around docs on default ssh user
1 parent d94d8c0 commit 5565a84

2 files changed

Lines changed: 8 additions & 6 deletions

File tree

README.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -87,6 +87,14 @@ on the `ssh` binary being in the path. This can be installed in a number of diff
8787
[built in version](https://docs.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse) on
8888
modern versions of windows.
8989

90+
# Using kssh with jumpboxes and bastion hosts
91+
92+
kssh does work correctly with jumpboxes and bastion hosts as long as they are configured to trust the SSH CA. For example,
93+
the command `kssh -J dev@jumpbox.example.com dev@server.internal` does work correctly. If you use an SSH config
94+
to manage your jumpbox configuration in a way that relies on using a specific user, it may be useful to specify a default
95+
user for kssh to use. For example, `kssh --set-default-user dev` will make it so that `kssh -J jumpbox.example.com server.internal`
96+
works correctly.
97+
9098
# Contributing
9199

92100
There are two separate binaries built from the code in this repo:

docs/troubleshooting.md

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -60,9 +60,3 @@ ssh-keygen \
6060
```
6161

6262
You can then use the signed SSH key to SSH via `ssh -i /path/to/key.pub user@server`.
63-
64-
## Using kssh with jumpboxes and bastion hosts
65-
66-
kssh does work correctly with jumpboxes and bastion hosts. Eg the command `kssh -J jumpbox.example.com server.internal`
67-
does work correctly. If using this with an SSH config, it may be useful to use `kssh --set-default-user foo` in order
68-
to specify a user to use for all kssh connections.

0 commit comments

Comments
 (0)