commit | a06c3fa8595873ecca812004c07e62e16e9a3ec3 | [log] [tgz] |
---|---|---|
author | Alex Ilin <alexilin@chromium.org> | Mon Jan 09 11:39:50 2023 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jan 09 11:39:50 2023 |
tree | c197286875432628438330c8ea0995c09cbb7e2d | |
parent | 33fea02cab755b9fd00cd33495085fd8313e8cdc [diff] |
[BSC] Add components/unexportable_keys This CL adds a new unexportable_keys component with a stub implementation of one of its main classes, UnexportableKeyTaskScheduler. This class facilitates work with crypto::UnexportableSigningKey which contains methods for creating encryption keys and signing data on a specialized secure hardware (TPM). This hardware can only process one command at a time, and some commands can run for a significant period of time. Thus, it's important to utilize TPM hardware as optimally as possible. All TPM commands issued by Chrome will go through a centralized UnexportableKeyTaskScheduler which schedules commands according to their priorities and ensures that cancelled commands don't get scheduled. This code is put in its own component because: 1) Another component (components/signin) is going to depend on it in the short term 2) We have another consumer not directly related to sign-in that will need it in the medium term (design is still in progress) 3) There are existing use-cases of crypto::UnexportableSigningKey that can be migrated to this component Bug: b/263249728 Change-Id: I84c8da341d24adba1bd8dd1cc6bbaa74a0d2f70c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4136194 Commit-Queue: Alex Ilin <alexilin@chromium.org> Reviewed-by: Colin Blundell <blundell@chromium.org> Reviewed-by: Adam Langley <agl@chromium.org> Reviewed-by: Monica Basta <msalama@chromium.org> Cr-Commit-Position: refs/heads/main@{#1090269}
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.