[TrustedVault] Implement device registration logic
This CL adds high-level device registration logic for trusted vault together with required interfaces/skeletons. Device has to be registered in order to silently follow further key rotations in the future. Device registration means generation of device key pair and sending public key to the server. Most recent vault key must be locally available in order to register the device. Currently, device registration is supported only for active sync account. Bug: 1102340 Change-Id: If7f6034db56752622bd108598a80c3e19681ba17 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339484Reviewed-by:Eric Orth <ericorth@chromium.org> Reviewed-by:
Marc Treib <treib@chromium.org> Commit-Queue: Maksim Moskvitin <mmoskvitin@google.com> Cr-Commit-Position: refs/heads/master@{#798583}
Showing
Please register or sign in to comment