From owner-freebsd-net@freebsd.org Thu May 26 13:26:37 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8DAD3B4BB0A for ; Thu, 26 May 2016 13:26:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7E1A71156 for ; Thu, 26 May 2016 13:26:37 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u4QDQarf000813 for ; Thu, 26 May 2016 13:26:37 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 166255] [net] [patch] It should be possible to disable "promiscuous mode enabled" messages Date: Thu, 26 May 2016 13:26:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 8.3-PRERELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: portmaster@bsdforge.com X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 May 2016 13:26:37 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D166255 --- Comment #24 from Chris Hutchinson --- (In reply to eugen from comment #21) > (In reply to Chris Hutchinson from comment #20) >=20 > You are essentially proposing the system to spend CPU time generating tons > of messages, pass them from the kernel to userland daemon using socket > subsystem and then spend more CPU time to filter them. Instead of just not > doing that all in expense of single extra tunnable. I'd just like to go on record as indicating that this is a security related issue, and one would *want* to know about it. In the rare case that this is *not* true. syslog(3) should be asked to deal with it. Has secteam@ weighed in on this? But given this bug has been closed, those of us whom are opposed to this change, will simply need to add a local patch to reverse it. Thank you for your indulgence. --Chris --=20 You are receiving this mail because: You are the assignee for the bug.=