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

Commit 90ceb94

Browse files
committed
Update README per feedback
1 parent 5565a84 commit 90ceb94

1 file changed

Lines changed: 12 additions & 5 deletions

File tree

README.md

Lines changed: 12 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -89,11 +89,18 @@ modern versions of windows.
8989

9090
# Using kssh with jumpboxes and bastion hosts
9191

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.
92+
kssh should work correctly with jumpboxes and bastion hosts as long as they are configured to trust the SSH CA and the usernames are correct. For example:
93+
94+
```
95+
kssh -J developer@jumpbox.example.com developer@server.internal
96+
```
97+
98+
This can also be made easier by setting the kssh default ssh-username locally, then you won't have to specify it for each server.
99+
100+
```
101+
kssh --set-default-user developer
102+
kssh -J jumpbox.example.com server.internal
103+
```
97104

98105
# Contributing
99106

0 commit comments

Comments
 (0)