login_manager: Add support for dev mode unblock broker

Initial changes to implement developer mode unblock broker
as part of carrier lock feature. Summary
- Implements logic  to unblock the developer mode in all the relevant
  places like FWMP, Crossystem and VPD.
- Implements DBus methods for clients to interact with the broker.
- Unit tests

BUG=b:239088539
TEST=Unit tests, tested with utilities like cryptohome, vpd etc.

Change-Id: I9374d282c5243e3c39be077074ad9c8a26c1ed15
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/3764383
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Tested-by: Ujjwal Pande <ujjwalpande@google.com>
Commit-Queue: Ujjwal Pande <ujjwalpande@google.com>
NOKEYCHECK=True
GitOrigin-RevId: 0558f4d0262e2707358ce17bfed74778d37568d7
1 file changed
tree: eafe3a25269d737a84a109d5e1d56025fa607706
  1. constants/
  2. dbus/
  3. mojo/
  4. src/
  5. switches/
  6. .gitignore
  7. BUILD.gn
  8. build.rs
  9. Cargo.toml
  10. LICENSE
  11. OWNERS
  12. README.md
  13. system_api.pc
README.md

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.