From 60d8aafcb1640e5dbfa30b7940a98a484d57cbd7 Mon Sep 17 00:00:00 2001 From: Damien Miller Date: Mon, 12 Nov 2001 11:04:05 +1100 Subject: - markus@cvs.openbsd.org 2001/11/07 22:12:01 [sshd.8] s/Keepalive/KeepAlive/; from openbsd@davidkrause.com --- sshd.8 | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'sshd.8') diff --git a/sshd.8 b/sshd.8 index c3a2e1ee4..d7e5937cf 100644 --- a/sshd.8 +++ b/sshd.8 @@ -34,7 +34,7 @@ .\" (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.8,v 1.153 2001/09/27 17:53:24 camield Exp $ +.\" $OpenBSD: sshd.8,v 1.154 2001/11/07 22:12:01 markus Exp $ .Dd September 25, 1999 .Dt SSHD 8 .Os @@ -402,11 +402,11 @@ reached while client alive messages are being sent, .Nm will disconnect the client, terminating the session. It is important to note that the use of client alive messages is very different from -.Cm Keepalive +.Cm KeepAlive (below). The client alive messages are sent through the encrypted channel and therefore will not be spoofable. The TCP keepalive option enabled by -.Cm Keepalive +.Cm KeepAlive is spoofable. The client alive mechanism is valuable when the client or server depend on knowing when a connection has become inactive. .Pp -- cgit v1.2.3