chrome.usb fails to open RFIDeas pcProx card reader |
||
Issue descriptionFeedback Report ID: 56119433039 According to the report, chrome.usb fails to open RFIDeas pcProx card reader: The device seems detected as a USB keyboard and claimed by the HID driver, which prevents chrome.usb from accessing it. [ 0.639651] usb 1-2: New USB device found, idVendor=0c27, idProduct=3bfa [ 0.639676] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 0.639695] usb 1-2: Product: USB Keyboard [ 0.639709] usb 1-2: Manufacturer: RFIDeas [ 0.639893] usb 1-2: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes [ 0.642864] input: RFIDeas USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/input/input3 [ 0.643027] hid-generic 0003:0C27:3BFA.0001: input,hidraw0: USB HID v1.10 Keyboard [RFIDeas USB Keyboard] on usb-0000:00:14.0-2/input0 One potential solution is to whitelist the device as ALLOW_DETACH through permission-broker. Alternatively, we may consider blacklisting the device from being a HID.
,
Mar 30 2017
> One potential solution is to whitelist the device as ALLOW_DETACH > through permission-broker. > Alternatively, we may consider blacklisting the device from being a HID. I'm not in favor of doing a one-off for this device, overall the behavior is on-purpose for our chrome.usb security model. There are several possible solutions for the RFIDeas pcProx reader (and other people are using it successfully) : 1. using the chrome.hid API which is intended for this use-case. 2. adding the device VID:PID to the UsbDetachableWhitelist policy through the cPanel 3. ordering the non-HID SKU of the RFID reader (ie RDR-6081AKU vs RDR-6082AKU) and use it from the chrome.usb interface We have definitely have customers having done either 2. or 3. I helped one of them doing 3., I have javascript examples somewhere.
,
Mar 30 2017
I definitely would like to see an HID example. I did try the HID API and I did not have success with that. However, that being said, I am truly not sure I had the manifest file correctly implemented for HID. I have attached the actual code we are using for the reader.
,
Mar 30 2017
> I have attached the actual code we are using for the reader. Given that's nearly character for character the code I wrote... Yes this version can work. Not sure where it came from, but it is missing the important bugfix I did in the last version of it: the 'buffer' should Uint8Array rather than Int8Array. but this code is for the solution 2. above (you need to declare the device in UsbDetachableWhitelist policy on the server administration console) |
||
►
Sign in to add a comment |
||
Comment 1 by benchan@chromium.org
, Mar 30 2017