From owner-freebsd-security Thu Mar 16 12: 0:50 2000 Delivered-To: freebsd-security@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 675A237BCBE for ; Thu, 16 Mar 2000 12:00:47 -0800 (PST) (envelope-from Doug@gorean.org) Received: from slave (doug@slave [10.0.0.1]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id MAA16673; Thu, 16 Mar 2000 12:00:26 -0800 (PST) (envelope-from Doug@gorean.org) Date: Thu, 16 Mar 2000 12:00:26 -0800 (PST) From: Doug Barton X-Sender: doug@dt051n0b.san.rr.com To: Dag-Erling Smorgrav Cc: Lawrence Sica , Rodrigo Campos , freebsd-security@FreeBSD.ORG Subject: Re: wrapping sshd In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 16 Mar 2000, Dag-Erling Smorgrav wrote: > Doug Barton writes: > > In all my years of running freebsd I've never seen inetd crash on any > > system. > > Weird, because inetd has historically been plagued with various > problems such as the infamous "junk pointer" bug. In all likelihood I've been very lucky on that count since I don't run much out of inetd, or run it at all if I can help it. The last two years or so I have been running more stuff out of inetd on my home systems (heavily firewalled, wrapped, etc.) more so to learn about utilities and such than anything else. On production systems I tend to use ssh exclusively. Currently at work however I'm installing more and more freebsd systems with inetd stuff open (once again, firewalled, wrapped, etc.) because in a mixed-platform, mixed-other-factors-too environment it has been deemed "necessary." I'm hoping I won't have to eat my words about not having it crash on me.... :) Doug -- "While the future's there for anyone to change, still you know it seems, it would be easier sometimes to change the past" - Jackson Browne, "Fountain of Sorrow" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message