From owner-freebsd-current  Sun Jun  6  0:23:40 1999
Delivered-To: freebsd-current@freebsd.org
Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162])
	by hub.freebsd.org (Postfix) with SMTP id D602514C9B
	for <freebsd-current@freebsd.org>; Sun,  6 Jun 1999 00:23:38 -0700 (PDT)
	(envelope-from sthaug@nethelp.no)
Received: (qmail 34794 invoked by uid 1001); 6 Jun 1999 07:23:37 +0000 (GMT)
To: scottm@cs.ucla.edu
Cc: wollman@khavrinen.lcs.mit.edu, freebsd-current@freebsd.org
Subject: Re: net.inet.tcp.always_keepalive on as default ? 
From: sthaug@nethelp.no
In-Reply-To: Your message of "Sat, 05 Jun 1999 18:27:17 -0700"
References: <199906060127.SAA00862@mordred.cs.ucla.edu>
X-Mailer: Mew version 1.05+ on Emacs 19.34.2
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Date: Sun, 06 Jun 1999 09:23:37 +0200
Message-ID: <34792.928653817@verdi.nethelp.no>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> The "poor sod" in this situation deserves something untoward,
> IMNSHO. Protocols like ssh do send something periodically whereas
> telnet doesn't. Telnet is a well-known security problem. As others
> have pointed out, this is an endemic problem in applications
> generally speaking, where a long-term "idle" connection isn't
> treated as an exception or an an error.

Some of us use only ssh for remote login *and* specifically turn off
ssh keepalives, in order to keep login sessions up for weeks at at time.

Steinar Haug, Nethelp consulting, sthaug@nethelp.no


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message