From owner-freebsd-arch Fri Jun 15 12:51:42 2001 Delivered-To: freebsd-arch@freebsd.org Received: from ringworld.nanolink.com (ringworld.nanolink.com [195.24.48.13]) by hub.freebsd.org (Postfix) with SMTP id 341CB37B406 for ; Fri, 15 Jun 2001 12:51:36 -0700 (PDT) (envelope-from roam@ringworld.nanolink.com) Received: (qmail 44226 invoked by uid 1000); 15 Jun 2001 19:50:12 -0000 Date: Fri, 15 Jun 2001 22:50:12 +0300 From: Peter Pentchev To: Mike Smith Cc: Dag-Erling Smorgrav , John Baldwin , arch@FreeBSD.ORG, audit@FreeBSD.ORG Subject: Re: new kldpath(8): display/modify the module search path Message-ID: <20010615225012.T94445@ringworld.oblivion.bg> Mail-Followup-To: Mike Smith , Dag-Erling Smorgrav , John Baldwin , arch@FreeBSD.ORG, audit@FreeBSD.ORG References: <200106151956.f5FJuiT01189@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200106151956.f5FJuiT01189@mass.dis.org>; from msmith@freebsd.org on Fri, Jun 15, 2001 at 12:56:44PM -0700 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Jun 15, 2001 at 12:56:44PM -0700, Mike Smith wrote: > > Peter Pentchev writes: > > > Or should there be a way to add a non-existent dir after all, > > > but only allowed by both -i and some other (-I? -f?) flag? > > > > Just add a -f (force) flag that disables checks. > > Don't check. Don't check what - don't check for a directory existence? This could lead to problems - theoretically at least, a startup script could add a not-yet-mounted directory, and then some user (who can see the contents of the kern.module_path sysctl) could mount his own directory there, and invoke a module load.. I know this is paranoid, but ldconfig already performs these checks, and ignores non-existent directories. It's true that ldconfig only makes the pass at invocation time, so it does not have to deal with the problem of adding a non-existent dir for future reference, but even so, ldconfig warns about the problem, which means kldpath/kldconfig should error out :) Or maybe I've misunderstood your "don't check" comment. If so, apologies for the wasted bandwidth :) G'luck, Peter -- I am not the subject of this sentence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message