@@ -12,11 +12,7 @@ description: |-
12
12
13
13
To ensure the SSH idle timeout occurs precisely when the
14
14
<tt>ClientAliveInterval</tt> is set, set the <tt>ClientAliveCountMax</tt> to
15
- value of <tt>0</tt>. This profile sets <tt>ClientAliveCountMax</tt> to
16
- <tt>{{{ xccdf_value("var_sshd_set_keepalive") }}}</tt>. To modify the
17
- <tt>ClientAliveCountMax</tt> option, edit <tt>/etc/ssh/sshd_config</tt> as
18
- follows:
19
- <pre>ClientAliveCountMax {{{ xccdf_value("var_sshd_set_keepalive") }}}</pre>
15
+ value of <tt>0</tt>.
20
16
21
17
rationale : |-
22
18
This ensures a user login will be terminated as soon as the <tt>ClientAliveInterval</tt>
@@ -59,8 +55,15 @@ ocil: |-
59
55
To ensure <tt>ClientAliveInterval</tt> is set correctly, run the following command:
60
56
<pre>$ sudo grep ClientAliveCountMax /etc/ssh/sshd_config</pre>
61
57
If properly configured, the output should be:
62
- <pre>ClientAliveCountMax {{{ xccdf_value("var_sshd_set_keepalive") }}}</pre>
63
- If the option is set to <tt>0</tt>, then the SSH idle timeout occurs precisely when
58
+ <pre>ClientAliveCountMax 0</pre>
59
+
60
+ In this case, the SSH idle timeout occurs precisely when
64
61
the <tt>ClientAliveInterval</tt> is set.
65
- If the option is set to a number greater than <tt>0</tt>, then the idle session will be disconnected after
66
- <tt>ClientAliveInterval * ClientAliveCountMax</tt> seconds.
62
+
63
+ template :
64
+ name : sshd_lineinfile
65
+ vars :
66
+ parameter : " ClientAliveCountMax"
67
+ value : " 0"
68
+ missing_parameter_pass : " false"
69
+ kubernetes : " off"
0 commit comments