From owner-freebsd-security Sat Dec 26 01:37:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA15743 for freebsd-security-outgoing; Sat, 26 Dec 1998 01:37:42 -0800 (PST) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from ol.kyrnet.kg (ol.kyrnet.kg [195.254.160.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA15738 for ; Sat, 26 Dec 1998 01:37:37 -0800 (PST) (envelope-from mlists@gizmo.kyrnet.kg) Received: from gizmo.kyrnet.kg (IDENT:mlists@gizmo.kyrnet.kg [195.254.160.13]) by ol.kyrnet.kg (8.9.1a/8.9.1) with ESMTP id OAA10282; Sat, 26 Dec 1998 14:05:55 +0600 Received: from localhost (mlists@localhost) by gizmo.kyrnet.kg (8.9.1a/8.9.1) with ESMTP id OAA27154; Sat, 26 Dec 1998 14:35:43 +0500 Date: Sat, 26 Dec 1998 14:35:43 +0500 (KGT) From: CyberPsychotic Reply-To: fygrave@tigerteam.net To: Barrett Richardson cc: freebsd-security@FreeBSD.ORG Subject: Re: Do I really need inetd? 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 ~ ~ I have all my necessary network services running as daemons. In the ~ face of recent discoveries of problems caused for inetd by nmap ~ and various things I've come to the conclusion that I really don't ~ need inetd -- another variable I can eliminated from the mix. ~ ~ Any undesirable side effects come to mind? nah.. not a one. I don't use inetd on some machines and very happy with it;) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message