On Sat, Apr 20, 2002 at 04:02:13PM -0600, Lyndon Nerenberg wrote: > >>>>> "Crist" == Crist J Clark <[EMAIL PROTECTED]> 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 | [EMAIL PROTECTED] | [EMAIL PROTECTED] http://people.freebsd.org/~cjc/ | [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message