Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 12 Aug 2002 23:02:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 12 Aug 2002 23:02:54 -0400 Received: from tmr-02.dsl.thebiz.net ([216.238.38.204]:20485 "EHLO gatekeeper.tmr.com") by vger.kernel.org with ESMTP id ; Mon, 12 Aug 2002 23:02:53 -0400 Date: Mon, 12 Aug 2002 23:00:30 -0400 (EDT) From: Bill Davidsen To: Helge Hafting cc: Pavel Machek , linux-kernel@vger.kernel.org Subject: Re: [2.6] The List, pass #2 In-Reply-To: <3D5233BC.96ABDF73@aitel.hist.no> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1121 Lines: 30 On Thu, 8 Aug 2002, Helge Hafting wrote: > Pavel Machek wrote: > > > > Lots of other bootup initialization, like DHCP, > > > might move to userspace as well. This gives a smaller > > > and safer kernel. > > > > Why *safer*? Partition (,DHCP,..) code is ran once at boot. It is hard for > > it to harm security. > > I wouldn't worry about partition detection, but network stuff > is always risky. A "bad guy" could listen for DHCP > and try to fake a response or do a buffer overflow. I don't really care about DHCP, but anything needed for booting is sure better off in the kernel. It can be a compile option for the embedded folks, but I suspect the code to call the user program is about as large as the code to actually check the partitions. -- bill davidsen CTO, TMR Associates, Inc Doing interesting things with little computers since 1979. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/