From owner-freebsd-current Thu Jul 8 0:18:30 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles551.castles.com [208.214.165.115]) by hub.freebsd.org (Postfix) with ESMTP id 0BE2914C01 for ; Thu, 8 Jul 1999 00:18:23 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id AAA01216; Thu, 8 Jul 1999 00:14:33 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199907080714.AAA01216@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Alex Zepeda Cc: Mike Smith , Keith Stevenson , freebsd-current@FreeBSD.ORG Subject: Re: userland ppp - startup In-reply-to: Your message of "Wed, 07 Jul 1999 23:26:53 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 08 Jul 1999 00:14:32 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > What reason would the rest of the "world" have to read rc.conf? It could > > > only create a possible security risk. > > > > This is shabby reasoning. rc.conf contains public system configuration > > data, which may need to be consumed by non-root processes. > > What kind of non-root program would need to consume rc.conf? Anything that wants access to paramters stored there. Visualise eg. a generic system monitoring script that checks the health of enabled services; any daemon running in a sandbox. Even rc.pccard could be run as non-root (modulo some changes to the way that ifconfig works). The point being that rc.conf is currently a public database, and until we have a better mechanism for managing parameter storage, it needs to stay that way. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message