From 632aeedefb3380e3753a6699fec0259346d6bbe1 Mon Sep 17 00:00:00 2001 From: David Thurstenson Date: Sat, 9 Mar 2024 03:18:16 +0000 Subject: [PATCH] docs: update dotfiles/ssh --- dotfiles/ssh.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/dotfiles/ssh.md b/dotfiles/ssh.md index 2a66a5c..f5b8499 100644 --- a/dotfiles/ssh.md +++ b/dotfiles/ssh.md @@ -2,7 +2,7 @@ title: OpenSSH description: Creature comfort configs for SSH published: true -date: 2024-03-08T01:57:19.739Z +date: 2024-03-09T03:18:14.841Z tags: editor: markdown dateCreated: 2024-03-07T23:21:49.285Z @@ -69,4 +69,5 @@ The `ServerAliveInterval` option sends a keepalive packet if no data has been re Additionally, the `ServerAliveCountMax` option specifies the number of keepalive packets that may be sent without a response before ssh terminates the connection. By default this is set to `3`, but if your connection is unreliable, you can set this higher to give your server a better chance at responding the next time a keepalive packet is sent. -It is important to note that messages sent by the `TTYKeepAlive` option are not sent through the encrypted channel and can be spoofed, but the "server alive" messages are sent through the encrypted channel and cannot be spoofed. Do not use `TTYKeepAlive` messages for determining the quality or security of a connection! See `ssh-config(5)` for more info. +> It is important to note that messages sent by the `TTYKeepAlive` option are not sent through the encrypted channel and can be spoofed, but the "server alive" messages are sent through the encrypted channel and can*not* be spoofed. Do not use `TTYKeepAlive` messages for determining the quality or security of a connection! See `ssh-config(5)` for more info. +{.is-danger}