usbconfig lack of device or permission

[Gary Jennejohn]

On Tue, 18 Sep 2018 12:14:29 +0530
shreyank amartya <shreyankfbsd at gmail.com> wrote:

> Okay, so I'm able to use usbconfig once I chown /dev/usb/*. I don't
> understand why adding my user to operator group is not enough instead of
> chowning everything.
> 

chown is the wrong approach.  You need to chmod 660 all the
entries under /dev/usb and add yourself to the operator group.

This is why adding yourself to the operator group does not
normally work:

ls -l /dev/usb/*
crw-------  1 root  operator  0x37 Sep 18 08:43 /dev/usb/0.1.0
crw-------  1 root  operator  0x7e Sep 18 08:43 /dev/usb/0.1.1
crw-------  1 root  operator  0x8d Sep 18 08:43 /dev/usb/0.2.0
[etc]

Only root has read/write permission.  The chmod also gives the
operator group read/write permission.

> On Mon, Sep 17, 2018 at 4:51 PM shreyank amartya <shreyankfbsd at gmail.com>
> wrote:
> 
> > > ^^ this is not root :-)  
> > If I log in as root, usbconfig works. I want to make it work when i'm
> > logged in as a normal user (amd).
> >  
> > > Expected, unless you chown the packet filtering devices.  
> > Please elaborate on how I can i do this?
> >
> > On Mon, Sep 17, 2018 at 4:39 PM Hans Petter Selasky <hps at selasky.org>
> > wrote:
> >  
> >> On 9/17/18 12:25 PM, shreyank amartya wrote:  
> >> > amd at amd-sham:~ % whoami
> >> > amd  
> >> ^^ this is not root :-)
> >>  
> >> >
> >> > amd at amd-sham:~ % usbdump -i usbus0 -s 255 -f 5
> >> > usbdump: Could not open BPF device: Permission denied  
> >>
> >> Expected, unless you chown the packet filtering devices.
> >>


-- 
Gary Jennejohn