From 3935385e2ad099aaef3eb95fc8850e8e4974bd5d Mon Sep 17 00:00:00 2001 From: Jake Howard Date: Sun, 4 Feb 2018 13:04:54 +0000 Subject: [PATCH] Remove sentence with bad link --- content/posts/opening-port-22.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/posts/opening-port-22.md b/content/posts/opening-port-22.md index 1f72cfe..00f367c 100644 --- a/content/posts/opening-port-22.md +++ b/content/posts/opening-port-22.md @@ -52,7 +52,7 @@ ssh -A intermediary-user@intermediary -W server-user@localhost:12345 After giving your credentials twice (once for the intermediary, then again for the final server), you should be met with a standard shell, on the destination server. #### Making connection easier -SSH has many configuration options available to ease this process, such as using keys for authentication over passwords, and transparently connecting to the intermediary server when trying to connect to the server. These techniques are most commonly used when interfacing with an [SSH Bastion](https://tenmilesquare.com/using-ssh-through-a-bastion-host-transparently/). +SSH has many configuration options available to ease this process, such as using keys for authentication over passwords, and transparently connecting to the intermediary server when trying to connect to the server. My personal tool of choice for managing config like this is [`assh`](https://github.com/moul/advanced-ssh-config).