Recreate identity if private key loading fails It seems like secureenclave keys can disappear from the keychain in, e.g., some backup and restore scenarios. This new logic will overwrite an old identity with a new one anytime the key loading fails (regardless of whether it was not found or some other issue). The current hypothesis is that the vast majority of these errors will be due to the key no longer existing on the device. Other metrics were landed to verify that hypothesis but, for now, this current change will attempt to overwrite all problematic keys. Bug: 414659932 Change-Id: I479ff24f8e830869204deb9fc8a2c975435be45d Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6519873 Reviewed-by: Hamda Mare <hmare@google.com> Commit-Queue: Sébastien Lalancette <seblalancette@chromium.org> Cr-Commit-Position: refs/heads/main@{#1457101}
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.