Date: Sun, 19 Aug 2001 20:23:10 -0400 (EDT) From: Robert Watson <rwatson@FreeBSD.ORG> To: Steven Ames <steve@virtual-voodoo.com> Cc: Igor Roshchin <str@giganda.komkon.org>, security@FreeBSD.ORG Subject: Re: cvs commit: src/etc inetd.conf Message-ID: <Pine.NEB.3.96L.1010819201942.34466C-100000@fledge.watson.org> In-Reply-To: <021401c1275e$99119540$28d90c42@eservoffice.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 17 Aug 2001, Steven Ames wrote: > So... not having heard any feedback... is it worth spending time on it > to produce patches to inetd (to handle Option #1) and a command line > tool to modify the configuration using either #1 or #2 (below)? Both > are pretty straight forward... Sorry for the delay in responding -- I'm on travel right now. I'm more interested in (2) right now as it maintains compatibility inetd on other platforms, as you suggest. If you build a set of utility routines that can support both a command line tool and a libdialog-based config tool (such as sysinstall), I think this would be great to include in the base system, as it would make it far easier for both new users and experienced users to understand the current configuration, and manage changes. Robert N M Watson FreeBSD Core Team, TrustedBSD Project robert@fledge.watson.org NAI Labs, Safeport Network Services 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.NEB.3.96L.1010819201942.34466C-100000>