shill: add fields to Passpoint credentials

Adds the provider Friendly Name and the credentials expiration time to
Passpoint credentials. The new fields are received through the D-Bus
API, and then stored with the credentials set.

BUG=b:253360225
TEST='FEATURES="test" emerge-${BOARD} chromeos-base/shill
tast run dut wifi.PasspointSelection.* wifi.PasspointRoaming.*'

Change-Id: I8ab95920ef863e0aa723f26524a775585cb1c222
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/4013779
Tested-by: Damien Dejean <damiendejean@google.com>
Reviewed-by: Hugo Benichi <hugobenichi@google.com>
Commit-Queue: Damien Dejean <damiendejean@google.com>
Reviewed-by: Jason Jeremy Iman <jasongustaman@chromium.org>
NOKEYCHECK=True
GitOrigin-RevId: 89508834348d794dee63e30a9eaa7a7ec02f5655
1 file changed
tree: 558d20f982c517d42d12076ff241e8bddd7fef56
  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.