From owner-freebsd-bugs@FreeBSD.ORG  Tue Aug 19 18:17:46 2014
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 9A3C8AF3
 for <freebsd-bugs@FreeBSD.org>; Tue, 19 Aug 2014 18:17:46 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 815E43F2A
 for <freebsd-bugs@FreeBSD.org>; Tue, 19 Aug 2014 18:17:46 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id s7JIHkGW046763
 for <freebsd-bugs@FreeBSD.org>; Tue, 19 Aug 2014 18:17:46 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 192827] `syslogd -s` listens on 514/udp6
Date: Tue, 19 Aug 2014 18:17:46 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: bin
X-Bugzilla-Version: 10.0-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: florian.ermisch@alumni.tu-berlin.de
X-Bugzilla-Status: Needs Triage
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-192827-8-bkButf470Y@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-192827-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-192827-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Aug 2014 18:17:46 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=192827

--- Comment #2 from florian.ermisch@alumni.tu-berlin.de ---
You're right, I just took a quite glance at the part of the manpage I've pasted 
earlier today and just read "Operate in secure mode.  Do not log messages from 
remote machines.  ... no network socket will be opened at all".
Maybe the "If specified twice" should be bold or something so it's harder to
overlook.

Can someone give me a usecase for `syslogd -s` (opening the upd-socket but 
apparently not logging received log messages)? I can't imagine any common 
usecase for this behaviour (only, like, "implementing a syslog-blackhole on
your 
network"). And '-s' only circumvents a malicious hosts filling the logservers 
disks with garbage but seems to still allow trafic to be directed at syslogd.

-- 
You are receiving this mail because:
You are the assignee for the bug.