-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSH options #103
Comments
Also looking to understand the intent of these values, specifically
Which makes me think the Edit: On rereading the docs, I understood it differently. If |
According to the manpages,
TCPKeepAliveSpecifies whether the system should send TCP keepalive messages ClientAliveCountMaxSets the number of client alive messages which may be sent ClientAliveIntervalSets a timeout interval in seconds after which if no data has |
The example SSH configuration has several options that (at least from my point of view) are not related to security and that do not have any written justification:
TCPKeepAlive no
(probably copied from http://web.archive.org/web/20200413100933/https://www.techbrown.com/harden-ssh-secure-linux-vps-server/ which does not provide a justification either)ClientAliveCountMax 0
Also, the suggested value of
ClientAliveInterval 300
is too high to ensure reliable connections from modern LTE ISPs (e.g., your friend's ISP) that have a ridiculously low NAT timeout, as low as 25 seconds.The text was updated successfully, but these errors were encountered: