system_api: Add BEAM_DEVICE_CERTIFICATE profile This commit introduces the BEAM_DEVICE_CERTIFICATE enum value to the CertificateProfile in attestation_ca.proto. This profile is intended for Project Beam meeting room devices and will be used to issue device-scoped certificates with the device's ADID in the Subject Common Name. Design Doc: go/beam_certificate_service_copy BUG=b:481063305 TEST=N/A Change-Id: Ia61e1f2c10fe8a304a8102bc3b15c2143288fb56 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/7539961 Reviewed-by: Yves Arrouye <drcrash@chromium.org> Reviewed-by: Courtney Wong <courtneywong@chromium.org> Tested-by: Ciara McMullin <ciaramcmullin@google.com> Reviewed-by: Matt Vertescher <mvertescher@google.com> Commit-Queue: Ciara McMullin <ciaramcmullin@google.com> NOKEYCHECK=True GitOrigin-RevId: f3ab58aaab04e1178d029a4760eda67f9e742d32
This directory (platform2/system_api) contains constants and definitions like D-Bus service names that are shared between Chromium and Chromium OS.
This directory is only for things like headers and .proto files. No implementation should be added.
When writting a .proto file make sure to use:
option optimize_for = LITE_RUNTIME;
This will force usage of a lite protobuf instead of a full/heavy weight protobuf. The browser only links against the light version, so you will get cryptic link errors about missing parts of Message if you define a protobuf here and then try to use it in Chrome. Currently CrOS links against the full protobuffer library, but that might change in the future.
When declaring a protobuf, avoid use of required unless it is exactly what you mean. “Required is Forever” and very rarely should actually be used. Consult Protocol Buffer Basics: C++ for a detailed of this issue.