Re: [linux-usb-devel] wireless mouse status: for non-root

2004-11-28 Thread Oliver Neukum
Am Montag, 29. November 2004 06:35 schrieb Pete Zaitcev: > On Sun, 28 Nov 2004 22:12:29 +, Sergey Udaltsov <[EMAIL PROTECTED]> wrote: > > > ghm... chmod really helped (most of the time I am real idiot:) - but I > > am not sure how to combine it with hotplug... AFAIK udev can easily be > > tune

Re: [linux-usb-devel] wireless mouse status: for non-root

2004-11-28 Thread Pete Zaitcev
On Sun, 28 Nov 2004 22:12:29 +, Sergey Udaltsov <[EMAIL PROTECTED]> wrote: > ghm... chmod really helped (most of the time I am real idiot:) - but I > am not sure how to combine it with hotplug... AFAIK udev can easily be > tuned to fix /udev/* permissions - but this is /proc filesystem, so > t

Re: [linux-usb-devel] wireless mouse status: for non-root

2004-11-28 Thread Sergey Udaltsov
ghm... chmod really helped (most of the time I am real idiot:) - but I am not sure how to combine it with hotplug... AFAIK udev can easily be tuned to fix /udev/* permissions - but this is /proc filesystem, so this is a bit tricky. Also, the biggest question is still about security - could this be

Re: [linux-usb-devel] wireless mouse status: for non-root

2004-11-28 Thread Oliver Neukum
Am Sonntag, 28. November 2004 22:53 schrieb Sergey Udaltsov: > Here it is: > > open("/proc/bus/usb/002/002", O_RDWR) = -1 EACCES (Permission denied) > open("/proc/bus/usb/002/002", O_RDONLY) = 3 > ioctl(3, USBDEVFS_CONTROL, 0xfef9e390) = -1 EPERM (Operation not permitted) > dup(2)

Re: [linux-usb-devel] wireless mouse status: for non-root

2004-11-28 Thread Sergey Udaltsov
Here it is: open("/proc/bus/usb/002/002", O_RDWR) = -1 EACCES (Permission denied) open("/proc/bus/usb/002/002", O_RDONLY) = 3 ioctl(3, USBDEVFS_CONTROL, 0xfef9e390) = -1 EPERM (Operation not permitted) dup(2) = 4 fcntl64(4, F_GETFL) = 0x2 (fl

Re: [linux-usb-devel] wireless mouse status: for non-root

2004-11-28 Thread Oliver Neukum
Am Sonntag, 28. November 2004 20:04 schrieb Sergey Udaltsov: > > Looking at the code it seems like libusb is used. > > Which error exactly does it fail? How is usbfs mounted? > $ mount | grep usb > usbfs on /proc/bus/usb type usbfs (rw) > $ lmctl -i > 003.003: 046d:c50e Receiver for MX1000 Laser (C

Re: [linux-usb-devel] wireless mouse status: for non-root

2004-11-28 Thread Sergey Udaltsov
> Looking at the code it seems like libusb is used. > Which error exactly does it fail? How is usbfs mounted? $ mount | grep usb usbfs on /proc/bus/usb type usbfs (rw) $ lmctl -i 003.003: 046d:c50e Receiver for MX1000 Laser (C-BN34) Caps: CSR SMS Writing to USB device: Operation not permitted Rega

Re: [linux-usb-devel] wireless mouse status: for non-root

2004-11-28 Thread Oliver Neukum
Am Sonntag, 28. November 2004 14:26 schrieb Sergey Udaltsov: > Ghm. The author or lmctl probably did not know about it:). He just > used this function in user-level code. So I really do not know which > was of dealing with kernel-level usb service it is using. > > Actually, in the code I just see

Re: [linux-usb-devel] wireless mouse status: for non-root

2004-11-28 Thread Sergey Udaltsov
Ghm. The author or lmctl probably did not know about it:). He just used this function in user-level code. So I really do not know which was of dealing with kernel-level usb service it is using. Actually, in the code I just see #define __KERNEL__ #include I do not really understand the question r

Re: [linux-usb-devel] wireless mouse status: for non-root

2004-11-28 Thread Oliver Neukum
Am Sonntag, 28. November 2004 12:01 schrieb Sergey Udaltsov: > Hi all > > I got logitech mx1000 wireless mouse. There is utility lmctl which > allows to read some mouse parameters - including the battery status. > The problem is that this utility uses usb_control_msg - which fails > beeing called

[linux-usb-devel] wireless mouse status: for non-root

2004-11-28 Thread Sergey Udaltsov
Hi all I got logitech mx1000 wireless mouse. There is utility lmctl which allows to read some mouse parameters - including the battery status. The problem is that this utility uses usb_control_msg - which fails beeing called from non-root (Fedora Core 3). Is there any workaround? Any non-protected