Date: Tue, 19 Nov 2002 21:03:47 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> To: Kris Kennaway <kris@obsecurity.org> Cc: kip@eventdriven.org, <current@FreeBSD.ORG> Subject: Re: Device permissions with DEVFS Message-ID: <20021119204920.G30290-100000@gamplex.bde.org> In-Reply-To: <20021119082758.GA3738@rot13.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 19 Nov 2002, Kris Kennaway wrote: > On Tue, Nov 19, 2002 at 12:16:49AM -0800, Kip Macy wrote: > > Sorry, if I'm repeating something already said, but > > the tone of your mail would indicate that I'm not. > > > > This doesn't sound like an intrinsic limitation of > > devfs, just an issue with how it is structured now. > > There should just be a central file for all the > > devices which devfs sucks in at build (or maybe boot) > > time specifying the appropriate permissions and any > > other configuration information. > > No, the default permissions are specified in the driver source code > via make_dev(). The drivers only get the magic numbers for uids and gids from a central file. This is bad enough. I think all devices should have ownership root:wheel and mode 0600, but that would increase the problems with non-persistent attributes. devfs(8) may be able to handle this now. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021119204920.G30290-100000>