From owner-freebsd-current Tue Feb 9 17:51:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17020 for freebsd-current-outgoing; Tue, 9 Feb 1999 17:51:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17009 for ; Tue, 9 Feb 1999 17:50:54 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id UAA18674; Tue, 9 Feb 1999 20:41:35 -0500 (EST) Date: Tue, 9 Feb 1999 20:41:35 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: mi@aldan.algebra.com cc: current@FreeBSD.ORG Subject: Re: DHCP, install, security, ICMP_BANDLIM In-Reply-To: <199902091603.LAA09757@misha.cisco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 9 Feb 1999, Mikhail Teterin wrote: > 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). This brings up something: shouldn't ICMP_BANDLIM be in the GENERIC kernel? > > -mi > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message