From owner-cvs-all Tue Dec 11 11:25: 6 2001 Delivered-To: cvs-all@freebsd.org Received: from westhost36.westhost.net (westhost36.westhost.net [216.71.84.209]) by hub.freebsd.org (Postfix) with ESMTP id 6FF0537B405 for ; Tue, 11 Dec 2001 11:25:02 -0800 (PST) Received: from localhost (haikugeek@localhost) by westhost36.westhost.net (8.11.6/8.11.6) with ESMTP id fBBJNgt31036 for ; Tue, 11 Dec 2001 13:23:42 -0600 Date: Mon, 10 Dec 2001 21:37:03 -0600 (CST) From: Jon Mini X-X-Sender: To: Mike Barcroft Subject: Re: cvs commit: src/sys/boot/i386/loader version src/share/examp In-Reply-To: <20011210221836.N1956@espresso.q9media.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 10 Dec 2001, Mike Barcroft wrote: > Mike Silbersack writes: > > > > Hm, I wonder if write enabling should even be compiled into the loader by > > default - I think you're correct in suspecting that changing /etc/passwd > > will be the primary use of this feature. :| > > Why would someone use this feature to write to the password file, when > they can just boot into single user mode and use their favourite > editor? The question that comes into my mind is this: Why would a process be able to write to /boot/*, but not /etc/*? Is it often that they gain this type of access? I'm not really sure any doors are being made any wider. However, for the paranoid, I could easily add an option that would only allow you to open files for writing that start with a certain path prefix or match an access list or something similar. -- Dizzy Cow (Jon Mini) dizzycow@haikugeek.com ... Desolation ... Despair ... Plastic Forks ... ~ ~ ~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message