Date: Sat, 20 Apr 2002 15:11:52 -0700 From: "Crist J. Clark" <crist.clark@attbi.com> To: Lyndon Nerenberg <lyndon@orthanc.ab.ca> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Adding a 'bpf' group for /dev/bpf* Message-ID: <20020420151152.E76898@blossom.cjclark.org> In-Reply-To: <200204202202.g3KM2DJ93468@orthanc.ab.ca>; from lyndon@orthanc.ab.ca on Sat, Apr 20, 2002 at 04:02:13PM -0600 References: <20020420145139.D76898@blossom.cjclark.org> <200204202202.g3KM2DJ93468@orthanc.ab.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Apr 20, 2002 at 04:02:13PM -0600, Lyndon Nerenberg wrote:
> >>>>> "Crist" == Crist J Clark <cjc@FreeBSD.ORG> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020420151152.E76898>