From owner-freebsd-security Sat Sep 12 02:33:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA14462 for freebsd-security-outgoing; Sat, 12 Sep 1998 02:33:57 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA14457 for ; Sat, 12 Sep 1998 02:33:55 -0700 (PDT) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 12397 invoked by uid 1001); 12 Sep 1998 09:33:41 +0000 (GMT) To: marquis@roble.com Cc: freebsd-security@FreeBSD.ORG Subject: Re: sshd In-Reply-To: Your message of "Fri, 11 Sep 1998 20:16:08 -0700 (PDT)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 12 Sep 1998 11:33:41 +0200 Message-ID: <12395.905592821@verdi.nethelp.no> Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The recommended sshd startup method used to be /etc/rc*(/*), probably > for historical reasons. It may still be a good idea on slow CPUs, > where it can take a while to generate a session key, or where > inetd.conf isn't running, however, in my experience, sshd is much more > reliably run from inetd. I believe it *is* still the recommended method, even on faster CPUs. I've used SSH since it came out, and I've found starting from /etc/rc*(/*) to very reliable. I actually have several machines whose *only* possibility of remote login is through ssh. It just runs and runs... Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message