cryptohome: Expose recovery_id history via dbus call.

This cl adds a dbus call to extract the history of recovery_ids
for a given user. It will be used to match the local history of
recovery attempts with the ledger data.

BUG=b:192786922
TEST=cros_run_unit_tests --board=${BOARD} --packages cryptohome

Change-Id: I5407fa5be41da0a1923fa639509c4ed2a9c43cc5
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/4003218
Reviewed-by: Maksim Ivanov <emaxx@chromium.org>
Reviewed-by: John Admanski <jadmanski@chromium.org>
Tested-by: Maciek Slusarczyk <mslus@chromium.org>
Commit-Queue: Maciek Slusarczyk <mslus@chromium.org>
NOKEYCHECK=True
GitOrigin-RevId: 70ada8046be10beb4d17680c6054b0e84db433c4
2 files changed
tree: 11fed0f91336f35c23ebd13e1535227a6378493d
  1. constants/
  2. dbus/
  3. mojo/
  4. src/
  5. switches/
  6. .gitignore
  7. BUILD.gn
  8. build.rs
  9. Cargo.toml
  10. DIR_METADATA
  11. LICENSE
  12. OWNERS
  13. README.md
  14. 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.