shill: Add DoH excluded and included domains manager properties

Add DOHExcludedDomains and DOHIncludedDomains to be passed from Chrome
to DNS proxy. The new properties are used to bypass DNS-over-HTTPS for
the specified domains.

The feature can be useful for deployments where a public DNS-over-HTTPS
DNS server is preferred by default, but internal plain-text DNS name
server is needed to resolve internal domains. One such use case is with
another other enteprise policy DNS-over-HTTPS with identifiers.

DD: go/cros-doh-bypass

BUG=b:351091814
TEST=CQ

Change-Id: I29f97583a6c957e81494405ca65fb522e5e8b681
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/5677951
Reviewed-by: Hugo Benichi <hugobenichi@google.com>
Commit-Queue: Jason Iman <jasongustaman@chromium.org>
Tested-by: Jason Iman <jasongustaman@chromium.org>
NOKEYCHECK=True
GitOrigin-RevId: 08e1393ea506794056d8357d535e27b52756eaf3
1 file changed
tree: 25a8395ccb8b5f429e2e4477d16d5f46ff03c6de
  1. constants/
  2. dbus/
  3. mojo/
  4. non_standard_ipc/
  5. proto/
  6. src/
  7. switches/
  8. .gitignore
  9. BUILD.gn
  10. build.rs
  11. Cargo.toml
  12. DIR_METADATA
  13. LICENSE
  14. OWNERS
  15. README.md
  16. 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.