From owner-freebsd-security Sat Dec 26 08:57:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11790 for freebsd-security-outgoing; Sat, 26 Dec 1998 08:57:35 -0800 (PST) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from roble.com (gw4.roble.com [199.108.85.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11785 for ; Sat, 26 Dec 1998 08:57:33 -0800 (PST) (envelope-from sendmail@roble.com) Received: from roble3.roble.com (roble3.roble.com [207.5.40.53]) by roble.com (Roble1b) with SMTP id IAA14952 for ; Sat, 26 Dec 1998 08:57:20 -0800 (PST) Date: Sat, 26 Dec 1998 08:57:17 -0800 (PST) From: Roger Marquis To: security@FreeBSD.ORG Subject: Re: Do I really need inetd? 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 "Kurt D. Zeilenga" wrote: >If you have IP aliases/addresses, I recommend you use the -a option such >that inetd only listens on address you expect the services to be obtained >under. > inetd -a 127.0.0.1 /etc/inetd-local.conf > ... The -a parameter is a great feature of FreeBSD inetd. I hope future versions will accept multiple IP addresses. Under 2.2.7, if you need to run an ftpd on say 12 specific IPs, you'll need to run 12 inetds. It would be cleaner if either one -a understood multiple IPs: inetd /etc/inetd.conf.ftp -a 192.168.1.10 192.168.1.11 [...] or if inetd understood multiple -a flags: inetd /etc/inetd.conf.ftp -a 192.168.1.10 -a 192.168.1.11 [...] -- Roger Marquis Roble Systems Consulting http://www.roble.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message