From owner-freebsd-security Mon Aug 24 09:33:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22369 for freebsd-security-outgoing; Mon, 24 Aug 1998 09:33:16 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from gatekeeper.iserver.com (gatekeeper.iserver.com [206.107.170.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22355 for ; Mon, 24 Aug 1998 09:33:13 -0700 (PDT) (envelope-from hart@iserver.com) Received: by gatekeeper.iserver.com; Mon, 24 Aug 1998 10:32:27 -0600 (MDT) Received: from unknown(192.168.1.109) by gatekeeper.iserver.com via smap (V3.1.1) id xma001284; Mon, 24 Aug 98 10:31:59 -0600 Received: (hart@localhost) by anchovy.orem.iserver.com (8.8.8) id KAA05433; Mon, 24 Aug 1998 10:32:08 -0600 (MDT) Date: Mon, 24 Aug 1998 10:32:08 -0600 (MDT) From: Paul Hart X-Sender: hart@anchovy.orem.iserver.com Reply-To: Paul Hart To: freebsd-security@FreeBSD.ORG Subject: Re: Scaring the bezeesus out of your system admin as a normal user: 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 On Fri, 21 Aug 1998, Ben wrote: > -s Operate in secure mode. Do not listen for log message from re- > mote machines. This is kind of a related question, but in 2.2.7-RELEASE syslogd appears to have been modified to bind to its UDP port even if it is run with the -s flag. It does discard packets received on the port (but still logs a message about it!), but should it not even bind to the port when running in secure mode? It didn't bind to the port in previous versions, if memory serves. If this was a recent design decision that is meant to last, I think I will hack my syslogd back to the way it used to be. Paul Hart -- Paul Robert Hart ><8> ><8> ><8> Verio Web Hosting, Inc. hart@iserver.com ><8> ><8> ><8> http://www.iserver.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message