Date: Thu, 16 Mar 2000 12:00:26 -0800 (PST) From: Doug Barton <Doug@gorean.org> To: Dag-Erling Smorgrav <des@flood.ping.uio.no> Cc: Lawrence Sica <larry@interactivate.com>, Rodrigo Campos <camposr@MATRIX.COM.BR>, freebsd-security@FreeBSD.ORG Subject: Re: wrapping sshd Message-ID: <Pine.BSF.4.21.0003161156540.16638-100000@dt051n0b.san.rr.com> In-Reply-To: <xzp4sa7i3cq.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On 16 Mar 2000, Dag-Erling Smorgrav wrote:
> Doug Barton <Doug@gorean.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0003161156540.16638-100000>