Date: Fri, 14 Jan 2000 17:21:05 +0200 From: Pekka Savola <Pekka.Savola@netcore.fi> To: freebsd-bugs@freebsd.org Subject: Re: bin/15414: syslogd -ss disables all network logging functions Message-ID: <3.0.6.32.20000114172105.0083e100@netcore.home> In-Reply-To: <20000114145733.DC8F71CA0@overcee.netplex.com.au> References: <Message from Dag-Erling Smorgrav <des@flood.ping.uio.no> <xzpiu0wohj9.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
>> What the originator really wants is -s, which instructs syslogd to >> open a socket but only use it for *sending* log messages. Incomig >> messages will be logged and discarded. One could argue that syslogd >> should not even bother with that, but it *has* to bind the socket >> because the receiving end will reject packets which do not originate >> from port 514, and there is no way to make the socket write-only >> (except maybe setting the receive buffer size to 0... I'll have to try >> that). > >Or 'open(); bind(); sendto(); close()' for each remote message.. This is what I want, yes. Before submitting this bug report, I had read the man page about syslogd -ss. However, this seemed like an unintended behaviour to me, since disabling remote logging altogether doesn't IMO enhance security, not opening a socket for receiving those would, on the other hand. Linux syslogd (1.3) does this by default: No remote receiving sockets are opened, but logging to remote servers is enabled. Pekka Savola pekkas@netcore.fi --- Across the nations the stories spread like spiderweb laid upon spiderweb, and men and women planned the future, believing they knew truth. They planned, and the Pattern absorbed their plans, weaving toward the future foretold. -- Robert Jordan: The Path of Daggers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.6.32.20000114172105.0083e100>