From owner-cvs-usrsbin Sat May 3 15:18:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA21473 for cvs-usrsbin-outgoing; Sat, 3 May 1997 15:18:39 -0700 (PDT) Received: from freefall.freebsd.org (freefall.cdrom.com [204.216.27.21]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA21420; Sat, 3 May 1997 15:18:05 -0700 (PDT) From: Joerg Wunsch Received: (from joerg@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA25401; Sat, 3 May 1997 15:17:43 -0700 (PDT) Date: Sat, 3 May 1997 15:17:43 -0700 (PDT) Message-Id: <199705032217.PAA25401@freefall.freebsd.org> To: CVS-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-usrsbin@FreeBSD.ORG Subject: cvs commit: src/usr.sbin/syslogd syslogd.8 syslogd.c Sender: owner-cvs-usrsbin@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk joerg 97/05/03 15:17:43 Modified: usr.sbin/syslogd syslogd.8 syslogd.c Log: Nobody ever seemed to be interested in reviewing these changes, and i found that my syslogd is now running them for several months... Add an option to syslogd to restrict the IP addresses that are allowed to log to this syslogd. It's too late to develop the inter-syslogd communications protocol mentioned in the BUGS section, some 10 years too late. Thus, restricting the IP address range is about the most effective change we can do if we want to allow incoming syslog messages at all. IMHO, we should encourage the system administrators to use this option, and thus provide a knob in /etc/rc.* for it, defaulting to -a 127.0.0.1/32 (just as a hint about the usage). Please state opinions about whether to merge this change into 2.2 or not (i've got it running on RELENG_2_2 anyway). Revision Changes Path 1.11 +75 -5 src/usr.sbin/syslogd/syslogd.8 1.25 +209 -5 src/usr.sbin/syslogd/syslogd.c