pyratelog

commit fa0a8502ad79b1f11d68703656175b0701ed1e6b
parent 862e783ed34dfe44b340c14d12ff9d029393fc54
Author: pyratebeard <root@pyratebeard.net>
Date:   Fri, 14 Jan 2022 23:30:28 +0000

ssh-aring_is_caring

Diffstat:
M
entry/ssh-aring_is_caring.draft
 | 
6
++++--

1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/entry/ssh-aring_is_caring.draft b/entry/ssh-aring_is_caring.draft
@@ -1,4 +1,4 @@
-Have you ever logged on to a server over SSH and have to type in your really long and complicated password (let us assume for some reason you haven't configured SSH keys and a key agent), then wanted to open a second connection to that same server only to type your long and complicated password again?
+Have you ever logged on to a server over SSH and had to type in your really long and complicated password (let us assume for some reason you haven't configured SSH keys and a key agent), then wanted to open a second connection to that same server only to type your long and complicated password again?
 
 What a pain in the ass.
 
@@ -17,6 +17,8 @@ Host *
 * `%h` - remote hostname
 * `%p` - remote port
 
+Further information on these and other options can be found in the ssh_config(5) man page.
+
 This session sharing will work until the initial connection is closed, after which all subsequent connections will close, so be careful.
 
 If you would rather the initial connection remain open in the background you can add the following to ~/.ssh/config
@@ -26,4 +28,4 @@ If you would rather the initial connection remain open in the background you can
 
 You will have to kill or close that connection using an alternative method, e.g. `ssh -O exit`.
 
-Read the `ssh_config(5)` man page for further information.
+Read the ssh_config(5) man page for further information.