From owner-freebsd-current Sat Apr 20 15:11:55 2002 Delivered-To: freebsd-current@freebsd.org Received: from rwcrmhc51.attbi.com (rwcrmhc51.attbi.com [204.127.198.38]) by hub.freebsd.org (Postfix) with ESMTP id E222237B400 for ; Sat, 20 Apr 2002 15:11:52 -0700 (PDT) Received: from blossom.cjclark.org ([12.234.91.48]) by rwcrmhc51.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with ESMTP id <20020420221152.VJKZ1143.rwcrmhc51.attbi.com@blossom.cjclark.org>; Sat, 20 Apr 2002 22:11:52 +0000 Received: (from cjc@localhost) by blossom.cjclark.org (8.11.6/8.11.6) id g3KMBqw77762; Sat, 20 Apr 2002 15:11:52 -0700 (PDT) (envelope-from cjc) Date: Sat, 20 Apr 2002 15:11:52 -0700 From: "Crist J. Clark" To: Lyndon Nerenberg Cc: freebsd-current@FreeBSD.ORG Subject: Re: Adding a 'bpf' group for /dev/bpf* Message-ID: <20020420151152.E76898@blossom.cjclark.org> Reply-To: cjclark@alum.mit.edu References: <20020420145139.D76898@blossom.cjclark.org> <200204202202.g3KM2DJ93468@orthanc.ab.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200204202202.g3KM2DJ93468@orthanc.ab.ca>; from lyndon@orthanc.ab.ca on Sat, Apr 20, 2002 at 04:02:13PM -0600 X-URL: http://people.freebsd.org/~cjc/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Apr 20, 2002 at 04:02:13PM -0600, Lyndon Nerenberg wrote: > >>>>> "Crist" == Crist J Clark writes: > > Crist> I do this a lot too on systems where it makes sense. But I'm > Crist> not sure I understand what you are asking to be done. Is it > Crist> asking too much of an administrator to do, > > There are two ways to handle this. One is to modify the ports builds to > conditionally create a 'bpf' group. This requires the ports all agree > on the group, and I don't like the idea of a port install messing with > permissions and ownerships of things in /dev (which aren't sticky across > reboots, anyway). If the OS sets the access policy there cannot be any > confusion. OK. Now you've really lost me. What do ports have to do with this? Which ports? None of the sniffing programs I am aware of use set{g,u}id bits. They rely on the permissions of the user running them. -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message