From owner-freebsd-net@freebsd.org Thu May 26 14:40:44 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 48736B4B355 for ; Thu, 26 May 2016 14:40:44 +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 3899B1D8E for ; Thu, 26 May 2016 14:40:44 +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 u4QEehuD000725 for ; Thu, 26 May 2016 14:40:44 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 14:40:44 +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 14:40:44 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D166255 --- Comment #26 from Chris Hutchinson --- (In reply to eugen from comment #25) > Default system behaviour is not changed. Reboot is required to disable > logging after a change to loader.conf. So, no patching should be required= to > stay safe. I understand that. I also agree with you that syslog(3) is not an ideal option, either. But as it stands, this new "switch" is still a security risk -- it opens a potential "backdoor", however unlikely some feel it might be. I'm just not sure that the need, outweighs the risk. Is there /really/ no other possible solution. Must a decision on this be made right now? Or could more time be given, in hopes a better solution might be found? Lastly, I know status of this bug is essentially "closed", and I apologize for responding so late. I would have responded earlier. But I was sure a patch in this direction, would have been rejected. --Chris --=20 You are receiving this mail because: You are the assignee for the bug.=