Chrome used to rely on an undocumented Windows feature to export wrapped
NCrypt keys to avoid storing metadata about them. This is risky: the
Windows API could stop working underneath us, and it doesn't work for
the software backend, so it's blocking crbug.com/398125798.
Instead, do the same thing we do on MacOS and generate a random
identifier for the key. When loading a TPM key, try to do it both by
name and from the wrapped key to support previously created keys.
Fixed: 398125799
Change-Id: I4747ba1b8777a11783d8bfe8937e0f1ed7a9bfb8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6297627
Reviewed-by: David Benjamin <davidben@chromium.org>
Commit-Queue: Nina Satragno <nsatragno@chromium.org>
Auto-Submit: Nina Satragno <nsatragno@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1424722}
829f87d7db