Make local key recovery / device registration expandable.

Introduce a LocalRecoveryFactor interface that supports recovering
Keychain keys from locally stored keys and registering the local device
as recovery factor. The logic around the physical device as recovery
factor is refactored into PhysicalDeviceRecoveryFactor which implements
LocalRecoveryFactor. StandaloneTrustedVaultBackend is extended to
support a list of LocalRecoveryFactor's for key retrieval.

This CL only introduces negligible behaviour changes (and thus no tests
were updated):
  * storage_->WriteDataToDisk() is called twice instead of a single time
    in StandaloneTrustedVaultBackend::StoreKeys().
  * storage_->WriteDataToDisk() is called twice instead of a single time
    as a result of MaybeRegisterDevice() (in the
    PhysicalDeviceRecoveryFactor::OnDeviceRegistered() and
    StandaloneTrustedVaultBackend::OnDeviceRegistered callbacks).
  * Generally, storage_->WriteDataToDisk() is often called instead of
    WriteDataToDiskAndNotify(). However, the "notify" part is only used
    in tests, and there are no tests which depend on notifications in
    the changed code paths.

Follow-up CLs will
  * Refactor UMA metrics to work for multiple local recovery factors.
  * Make StandaloneTrustedVaultBackend support multiple local recovery
    factors for device registration.
  * Add tests for various cases when multiple local recovery factors are
    present.
  * Add a second LocalRecoveryFactor which will use the iCloud Keychain
    on MacOS for registration / key retrieval.

Bug: b:398160323
Change-Id: Ib242924d3ade19b1dc8e6c67bc00735bd80ce32a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6368662
Reviewed-by: Mohamed Amir Yosef <mamir@chromium.org>
Commit-Queue: Thomas Thrainer <thomasth@google.com>
Reviewed-by: Maksim Moskvitin <mmoskvitin@google.com>
Cr-Commit-Position: refs/heads/main@{#1437544}
10 files changed
tree: ae033e5595df704c680913f15a6965531903cf8e
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. .clang-format
  50. .clang-tidy
  51. .clangd
  52. .git-blame-ignore-revs
  53. .gitallowed
  54. .gitattributes
  55. .gitignore
  56. .gitmodules
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. CPPLINT.cfg
  68. CRYPTO_OWNERS
  69. DEPS
  70. DIR_METADATA
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure.

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.

If you found a bug, please file it at https://crbug.com/new.