Date: Fri, 15 Jun 2001 22:50:12 +0300 From: Peter Pentchev <roam@orbitel.bg> To: Mike Smith <msmith@freebsd.org> Cc: Dag-Erling Smorgrav <des@ofug.org>, John Baldwin <jhb@FreeBSD.ORG>, arch@FreeBSD.ORG, audit@FreeBSD.ORG Subject: Re: new kldpath(8): display/modify the module search path Message-ID: <20010615225012.T94445@ringworld.oblivion.bg> In-Reply-To: <200106151956.f5FJuiT01189@mass.dis.org>; from msmith@freebsd.org on Fri, Jun 15, 2001 at 12:56:44PM -0700 References: <xzp4rthjzrc.fsf@flood.ping.uio.no> <200106151956.f5FJuiT01189@mass.dis.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 15, 2001 at 12:56:44PM -0700, Mike Smith wrote: > > Peter Pentchev <roam@orbitel.bg> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010615225012.T94445>