New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 638363 link

Starred by 5 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Feature



Sign in to add a comment

[FR] Device Policy to Allow/Disallow USB Peripherals for CrOS Users

Project Member Reported by c...@chromium.org, Aug 16 2016

Issue description

This feature request will allow you to specify a list of USB devices that can ONLY be accessed by Chrome OS users. You could list devices such as keyboards, signature pads, printers and scanners, as well as other USB devices. Consideration for this "Device" policy should default to (1) allow all peripherals, (2) disallow all except for USB devices I specify as denoted below.

To add devices to the deivce policy list, enter the USB vendor identifier (VID) and product identifier (PID), as a colon separated hexadecimal pair (VID:PID), for each device on a separate line. For example, to list a mouse with a VID of 046E and a PID of D626, and a signature pad with a VID of 0404 and PID of 6002, enter the following in the device policy text box for allowed usb peripherals:

046E:D626
0404:6002



 

Comment 1 by c...@chromium.org, Aug 16 2016

Cc: sduraisamy@chromium.org
This should not be too hard and would follow along the lines of 

https://code.google.com/p/chrome-os-partner/issues/detail?id=50249
Cc: vpalatin@chromium.org

Comment 4 by saswat@chromium.org, Nov 10 2016

Cc: -saswat@chromium.org
We need this feature for kiosk app mode as well. Not just user setting.

Comment 6 by po.c...@hkmci.com, Sep 29 2017

Any update from the product team? We are doing a Chrome device deployment right now and this feature is very critical to us. The user policy cannot help me...

It would be great if this feature request is already on roadmap.Thanks!

Comment 7 by vpalatin@google.com, Sep 29 2017

What is your use case ?
It's very unclear to me what it can be.
The Chrome device deployment use case which po.chan@hkmci.com mentioned is, the chrome devices are placed at some public area, and customer's chrome app is running on the devices. There is an USB card reader plugged in to the device in order to let their staff to swipe card and communicate with the app. However customer would like to only allow the card reader to be recognised by the device. If someone tried to plugin another type of USB devices into the chrome device, they want to block the usb devices. So a whitelisting to usb VID:PID will be useful for them to just restrict everything but the card reader. Since the app is a single kiosk app so that means no user login is required, it will be great to have such feature implemented into "Device Setting" as well.
> However customer would like to only allow the card reader to be recognised by the device.

What is the actual end goal of this requirement ?
Components: Enterprise
Status: Assigned (was: Untriaged)
Owner: marcuskoehler@chromium.org

Sign in to add a comment