commit | d5718944a247a998d5fe565a66367a2021201fa0 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@chromium.org> | Wed Apr 16 20:44:33 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 16 20:44:33 2025 |
tree | 89a0417107dbd3c7e7650979789a55a7d212872e | |
parent | 799be5e132eb36551b4bd2b9d1b89d1b1b7e7595 [diff] |
Disable the deprecated SecIdentitySearchCreate codepaths in ClientCertStoreMac macOS provides two ways to search for identities, SecItemCopyMatching() and SecIdentitySearchCreate(). SecIdentitySearchCreate() is deprecated, as it relies on CSSM_KEYUSE_SIGN (part of the deprecated CDSM/CSSA implementation). We used to merge the results of the old and new APIs, to account for any identities that were not returned by SecItemCopyMatching(), particularly smartcard-based identities. It is unclear whether such identities still exist, but the APIs have been deprecated since 10.7. Disable the old codepath on the assumption that Apple's APIs behave as documented. If we run into issues, I've left a base::Feature that can turn the codepath back on as needed. This is a speculative fix for crbug.com/408462957, which is a crash somewhere in Apple's system libraries, via this deprecated codepath. Bug: 40233280, 408462957 Change-Id: Ic64a1a048a469288b582767394f3cc82fada0a19 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6462461 Commit-Queue: Matt Mueller <mattm@chromium.org> Commit-Queue: David Benjamin <davidben@chromium.org> Reviewed-by: Matt Mueller <mattm@chromium.org> Auto-Submit: David Benjamin <davidben@chromium.org> Cr-Commit-Position: refs/heads/main@{#1447988}
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.