commit | 18cd84f099e46ce52e272cb15b2efbf3e1bbd1a4 | [log] [tgz] |
---|---|---|
author | Ted Brandston <tbrandston@google.com> | Wed Oct 18 14:26:32 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Oct 18 14:26:32 2023 |
tree | 131858ead929947064d45130302cd8218c64e528 | |
parent | 3fe2752a5365b8ac1cc479071d4a04ba0438c696 [diff] |
[ChromeOS Flex] Add device policy for sending hw data This adds a new device policy for managed ChromeOS Flex devices to control whether detailed hardware component data can collected for product improvement purposes. We'd like the administrator to be very clear on what the data will be used for, and not piggy-back on other policies that allow data collection intended for customer use. This is Flex-only, sending hardware data, for product improvement. Device policies should start with "Device", according to a comment in src/chromium/src/components/policy/tools/syntax_check_policy_template_json.py Boolean policies end with "Enabled" by convention? So our policy name: `DeviceFlexHwDataForProductImprovementEnabled`. Although docs/enterprise/add_new_policy.md says we need to add a preference and register it in Local State, etc. that doesn't appear to be necessary for Device policies. Tested by copying the chrome_device_policy.proto to a cros_sdk, and building libbrillo (with added accessors) against it, then using the new accessors to check value. Change-Id: I49282724a216cf36a09b784f174d0f4c9d589c43 Bug: b:299148409 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4908296 Reviewed-by: Roland Bock <rbock@google.com> Reviewed-by: Maksim Ivanov <emaxx@chromium.org> Commit-Queue: Ted Brandston <tbrandston@google.com> Auto-Submit: Ted Brandston <tbrandston@google.com> Cr-Commit-Position: refs/heads/main@{#1211486}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.