From owner-freebsd-questions Sun Nov 3 13:24:07 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id NAA26341 for questions-outgoing; Sun, 3 Nov 1996 13:24:07 -0800 (PST) Received: from delphi.bsd.uchicago.edu (delphi.bsd.uchicago.edu [128.135.5.5]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id NAA26296 for ; Sun, 3 Nov 1996 13:23:57 -0800 (PST) Received: from bio-5.bsd.uchicago.edu (bio-5.bsd.uchicago.edu [128.135.75.14]) by delphi.bsd.uchicago.edu (8.7.6/8.7.3/BSD-4.0) with SMTP id PAA10583 for ; Sun, 3 Nov 1996 15:23:31 -0600 (CST) Received: by bio-5.bsd.uchicago.edu (5.0/SMI-SVR4) id AA06470; Sun, 3 Nov 1996 15:23:29 +0600 Date: Sun, 3 Nov 1996 15:23:29 +0600 Message-Id: <9611032123.AA06470@bio-5.bsd.uchicago.edu> To: questions@freebsd.org Subject: group ownership on /dev/io, /dev/mem, /dev/console From: Tim Pierce Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm working on the FreeBSD port of MGR, the small Bellcore window system. In order to function properly on FreeBSD, the mgr server needs to have access to /dev/io, /dev/mem and /dev/console. One option is to run it as root, but another I've considered is setting the group ownerships on these files to `mgr', adding group read/write permission to each one, and making the mgr server binary setgid to group `mgr'. This worked all right in an initial test, but I'm concerned about hidden dangers. Will the system be compromised or unable to run by fiddling with the group ownerships on these files? love, T.