From owner-freebsd-current Tue Feb 9 08:08:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03002 for freebsd-current-outgoing; Tue, 9 Feb 1999 08:08:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA02975 for ; Tue, 9 Feb 1999 08:08:26 -0800 (PST) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.1/8.9.1) id LAA09757 for current@freebsd.org; Tue, 9 Feb 1999 11:03:25 -0500 (EST) (envelope-from mi) From: Mikhail Teterin Message-Id: <199902091603.LAA09757@misha.cisco.com> Subject: DHCP, install, security To: current@FreeBSD.ORG Date: Tue, 9 Feb 1999 11:03:25 -0500 (EST) Reply-To: mi@aldan.algebra.com X-Mailer: ELM [version 2.4ME+ PL52 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How about putting bpf functionality into install-kernel, but not into the GENERIC kernel? If the install required the use of dhcp, sysinstall should yell about having to rebuild the kernel with bpf-device in. On the other hand, the security-concerned ISPs and others can rebuild their kernels to remove the bpf (they probably rebuild them anyway for other reasons, or should do that anyway). -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message