upstream: Change description of TCPKeepAlive from "inactive" to
"unresponsive" to clarify what it checks for. Patch from jblaine at kickflop.net via github pr#129, ok djm@. OpenBSD-Commit-ID: 3682f8ec7227f5697945daa25d11ce2d933899e9
This commit is contained in:
parent
7afc45c3ed
commit
8fdbc7247f
|
@ -33,8 +33,8 @@
|
|||
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
|
||||
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.\" $OpenBSD: ssh_config.5,v 1.297 2019/08/02 01:23:19 djm Exp $
|
||||
.Dd $Mdocdate: August 2 2019 $
|
||||
.\" $OpenBSD: ssh_config.5,v 1.298 2019/08/09 04:24:03 dtucker Exp $
|
||||
.Dd $Mdocdate: August 9 2019 $
|
||||
.Dt SSH_CONFIG 5
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -1460,7 +1460,7 @@ The TCP keepalive option enabled by
|
|||
.Cm TCPKeepAlive
|
||||
is spoofable.
|
||||
The server alive mechanism is valuable when the client or
|
||||
server depend on knowing when a connection has become inactive.
|
||||
server depend on knowing when a connection has become unresponsive.
|
||||
.Pp
|
||||
The default value is 3.
|
||||
If, for example,
|
||||
|
|
|
@ -33,8 +33,8 @@
|
|||
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
|
||||
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.\" $OpenBSD: sshd_config.5,v 1.287 2019/07/23 23:06:57 dtucker Exp $
|
||||
.Dd $Mdocdate: July 23 2019 $
|
||||
.\" $OpenBSD: sshd_config.5,v 1.288 2019/08/09 04:24:03 dtucker Exp $
|
||||
.Dd $Mdocdate: August 9 2019 $
|
||||
.Dt SSHD_CONFIG 5
|
||||
.Os
|
||||
.Sh NAME
|
||||
|
@ -512,7 +512,7 @@ The TCP keepalive option enabled by
|
|||
.Cm TCPKeepAlive
|
||||
is spoofable.
|
||||
The client alive mechanism is valuable when the client or
|
||||
server depend on knowing when a connection has become inactive.
|
||||
server depend on knowing when a connection has become unresponsive.
|
||||
.Pp
|
||||
The default value is 3.
|
||||
If
|
||||
|
|
Loading…
Reference in New Issue